Skip to main content

WhatsApp Flows

WhatsApp Flows are static forms published to Meta (Static · Without endpoint). They are not the same as Bot Flows (scripted automations under Settings → Bot Flows or Automations → WhatsApp).

Dynamic endpoint Flows are not supported in Kazenly today.

Open WhatsApp Flows​

  1. In the sidebar, open Broadcasts.
  2. Under Send, select Flows (next to Templates).

Page title: WhatsApp Flows

The list shows first (same pattern as Templates and Campaigns), with search and status filters. Click New Flow to create. Empty list: No Flows yet.

Each row can View, Edit, Publish, or Refresh. View opens an approximate on-device preview (radios, text fields, dropdowns, multi-screen picker). Interaction stays in Kazenly — nothing is sent to Meta from preview.

Only a Published Flow can be attached to a template or sent from a chat.

Create or edit a Flow​

New Flow / Edit Flow replaces the list (not stacked above it).

Lead line for create: Static · Without endpoint — visual editor (multi-screen), paste JSON, or import a Meta Flow ID.

Tabs:

TabUse when
Visual editorBuild a static Flow on screen (Add Screen for multi-screen). Live preview updates as you edit.
Paste JSONPaste Meta Flow JSON, or Upload JSON File for large multi-screen exports. Character count is shown; there is no length limit.
Import Meta IDAttach a Flow that already exists in Meta by Meta Flow ID.

In the visual editor, Short text and Long text fields support a character limit that Meta accepts on publish (short text and long text use Meta’s separate limit rules).

Switching Visual editor ↔ Paste JSON keeps both in sync when the JSON uses supported components. Unsupported multi-screen or unknown components stay on Paste JSON with an error — you can still Register static multi-screen JSON.

If paste includes dynamic endpoint markers (data_api_version), use Convert To Static before Register. That strips endpoint markers so the Flow is static.

Save buttons:

ModeButton
Visual editorRegister (create) or save from the form
Paste JSONSave JSON / Register
Import Meta IDImport

If the JSON is not valid: Flow JSON is not valid. If the name is already used on this WhatsApp account, choose another name or import by Meta ID.

Use a published Flow​

  • On a Utility or Marketing template, Add Flow — see Templates. Authentication templates cannot use a Flow button.
  • From an open WhatsApp chat, while the 24-hour window is still open, use Send WhatsApp Flow. Outside that window, send a template with a Flow button instead.

When the customer submits the form, the chat shows a read-only FLOW bubble labelled Submitted, with their answers. Agents cannot edit those answers. Conversation History shows the same Flow invite / submit bubbles as the live chat.

Save answers to contact (Forms detail)​

Open a Flow’s details (View). Admins and managers see Save answers to contact:

  • Lead: Maps this Form’s answers to Contact Fields on every submit — including campaign and inbox sends. Bot canvas mappings still apply when a bot is waiting on this Form.

  • Map each answer to a contact field, — skip —, or + Create new field…

  • Answer lists include fields inside If / Switch branches (not only the default screen path). Phone preview walks those branches the same way. When you choose + Create new field…, a New contact field panel opens (Forms detail and bot Send WhatsApp Flow use the same picker):

  • Name (required) — prefilled from a readable form of the answer label; edit freely. Error: Name is required

  • Key — starts from the name as a slug; edit anytime. Hint: Lowercase letters, numbers, underscore · max 64. Errors include Key is required, Key must be at most 64 characters, Key must use only lowercase letters, numbers, and underscores, A contact field with this key already exists

  • Type — text (fixed for this create path)

  • Sensitive — optional checkbox

  • Create field (Creating…) saves the field; Cancel closes without creating anything. The field is created only when you confirm — not automatically from the Meta answer name.

  • After mappings are set, click Save field mapping (Saving… while in progress). Success: Saved. Campaign and inbox Form submits will write these fields.

  • Empty answers: No answer fields found on this Flow JSON. Publish or refresh after editing screens.

Bot live-wait mappings still sit on the bot Send WhatsApp Flow step. Journey: Use Contact Fields End to End.

A Bot Flow can also send a published WhatsApp Flow as a step, map answers under Save answers to contact, then branch on the answers — see Bot Flows and Contact Fields.