WhatsApp Flows
Send WhatsApp Flow templates, read customer submissions in the Inbox, and trigger workflows from the answers.
WhatsApp Flows are native, multi-screen forms that open right inside WhatsApp — booking pickers, lead forms, feedback surveys — no browser, no external link. The customer taps a button on your message, fills in the screens, hits submit, and the answers come back into the same chat.
Cloodot works with flows end to end:
- Send any approved template that has a Flow button — in one-off messages, campaigns, workflow actions, and the developer API.
- Read each completed submission in the Inbox, field by field.
- Automate on the answers with the WhatsApp Flow Submitted workflow trigger.
Flows themselves are built and published in Meta's tooling — Cloodot doesn't create or preview flow screens. Design the flow in WhatsApp Manager → Flows (Meta's Flow Builder), attach it to a message template as a Flow button, and get the template approved. Once the template syncs into Cloodot it behaves like any other template.
Send a flow template
There is nothing to configure. A template with a Flow button works everywhere templates work:
- One-off — New message from the Inbox: pick the template, fill the usual header and body variables (the Flow button needs none), and send.
- Campaigns — pick the template in the campaign builder; every recipient gets the same Flow button. See Campaigns.
- Workflows — the Send WhatsApp Template action sends flow templates too.
- Developer API — template sends through the public API include the Flow button automatically.
In previews the Flow button shows with a form icon. On the customer's phone, tapping it opens the flow full-screen inside WhatsApp.
Cloodot stamps every flow send with a unique token, which is how a later submission is traced back to the campaign or template that produced it (see the trigger variables below).
Read submissions in the Inbox
A completed flow arrives in the conversation as a Native Flow Message chip showing how many fields were submitted. Click it to open a drawer with every question and answer, ready to copy.
The AI agent sees the submitted answers as conversation context too, so its replies and extractions can use them.
Trigger workflows from submissions
The WhatsApp Flow Submitted trigger fires every time a customer completes a flow in a conversation — whichever surface sent it. Use it to route, label, notify, or write the answers into contact fields.
Trigger variables
| Variable | What it holds |
|---|---|
{{trigger.flowValues.<field>}} | A submitted answer, by its field name from the flow — e.g. {{trigger.flowValues.km_range}}. Multi-select answers are comma-joined. |
{{trigger.flowSource}} | Where the flow was sent from: oneoff, campaign, workflow, sample, api — or unknown when the flow wasn't sent through Cloodot. |
{{trigger.campaignId}} | The campaign that sent the flow, for campaign sends. |
{{trigger.templateName}} | The template whose Flow button opened the flow, when known. |
{{trigger.flowToken}} | The raw send token, if you need it for external correlation. |
The standard conversation context — {{trigger.conversationId}}, {{trigger.contactName}}, {{trigger.contactPhone}}, and friends — is there as well.
Match on the answers
The trigger fires for every submission; branch on the answers with a Decision node using a Variable condition. For example, a service-booking flow:
- Trigger: WhatsApp Flow Submitted
- Decision: variable
trigger.flowValues.pickupequalsyes - Yes → Add Label
pickup-requestedand Assign to User · No → Send Message with drop-off instructions
To react to one specific flow only, add a condition on trigger.templateName (or trigger.campaignId to scope to a single campaign).
Related topics
- WhatsApp Templates — sync and manage the templates that carry Flow buttons
- Campaigns — send a flow to a whole segment
- Workflows — everything triggers and actions can do