Publish flow
Publish a DRAFT flow. This is irreversible. Once published, the flow and its JSON become immutable and the flow can be sent to users. To update a published flow, create a new flow (optionally cloning this one via cloneFlowId).
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Flow ID
WhatsApp social account ID
Response Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.whatsappflows.publishWhatsAppFlow({ path: { flowId: 'flow_abc123', }, body: { accountId: 'account_abc123', },});console.log(data);{
"success": true
}{
"error": "Unauthorized"
}List flow versions GET
List the flow's version history (the clone lineage Zernio tracks, since Meta has no native versioning), newest version first. Each entry is enriched with the version's live name and status from Meta. A flow with no lineage returns just itself as version 1.
Deprecate flow POST
Deprecate a PUBLISHED flow. This is irreversible. Deprecated flows cannot be sent or opened, but existing active sessions may continue until they complete.