Skip to main content

WhatsApp & flows steps

Steps under WhatsApp & flows cover WhatsApp-specific messaging and reusable ChatMaven sub-flows.

Live URL: live.chatmaven.ai/workspaces/flows

WhatsApp-only steps

WhatsApp Template and WhatsApp Flow run on WhatsApp only—they are skipped on Web Chat. Scope the parent flow to WhatsApp in Channels, select the correct agent(s), and pick a WhatsApp integration phone number in the builder header. See Flows overview — WhatsApp integration.

There is no separate ChatMaven Template palette step. Send workspace template content via Message (template picker) or WhatsApp Template. See Templates.

WhatsApp Template​

Send a WhatsApp-approved template with variables.

WhatsApp Template step in the flow builder

  1. Sync and approve templates under your agent's WhatsApp integration. See WhatsApp Templates.
  2. In the flow header, scope to WhatsApp and select the WhatsApp integration phone number.
  3. Add WhatsApp Template to the canvas.
  4. Select the template and language (for example en).
  5. Map template variables to flow variables or static text.
  6. Configure On send error and Delivery wait as needed.
  7. Save the step.

Tips:

  • Templates are required for many business-initiated messages outside the customer service window.
  • Match variable count and order to the approved template.
  • For web chat and WhatsApp in one logical journey, use Condition to branch: Message on web chat, WhatsApp Template on WhatsApp.

WhatsApp Flow​

Launch a Meta WhatsApp Flow created in WhatsApp Manager.

WhatsApp Flow step in the flow builder

  1. Create and publish the flow in WhatsApp Manager. See WhatsApp Flow.
  2. In ChatMaven, Sync flows on the agent WhatsApp integration if needed.
  3. Scope the parent flow to WhatsApp and select the WhatsApp integration phone number.
  4. Add WhatsApp Flow to the canvas and select the synced Meta flow.
  5. Set Message body, Flow button label, and optional Form submit timeout.
  6. Wire Success, Timeout, and Failure ports on the canvas as needed.
  7. Save the step.

Tips:

  • Test on the same WhatsApp number configured in the flow header.
  • When timeout is greater than zero and the Timeout port is wired, the flow follows that branch if the contact does not submit the Meta form in time.

ChatMaven Flow (nested)​

Run another ChatMaven flow in the same workspace from the current point in the journey. Works on all channels (not WhatsApp-only). Use it to reuse welcome paths, compliance snippets, or sub-menus without copying nodes.

ChatMaven Flow nested step settings

  1. Add ChatMaven Flow from STEPS under WhatsApp & flows.
  2. Click the node and set:
FieldOptions
Target flowAnother saved flow in the workspace (for example a short welcome child flow).
When child flow endsReturn to parent flow (continue at next step) — resume the parent after the child finishes. Leave parent paused (user taps Resume) — parent waits until an agent or contact resumes.
Step gapDelay before the child starts: 250 ms, 500 ms, 1–5 seconds.
  1. Connect the child step's outgoing edge to where the parent should continue when returning automatically.
  2. Save the step, then Save the flow.

Tips:

  • Keep child flows focused (one welcome, one consent, one sub-menu).
  • Avoid loops: child flow triggers or nested steps must not re-fire the parent trigger indefinitely.
  • Name child flows clearly (for example Welcome - Child Flow).
  • Align agent and channel scope so the child can run in the same conversation context.
ChatMaven Flow vs WhatsApp Flow

ChatMaven Flow runs another ChatMaven canvas. WhatsApp Flow launches a Meta interactive form on WhatsApp only.