Build bot flows that reply to incoming messages automatically, and create forms that open inside WhatsApp (Meta Flows).
What is this section for?
Flows brings two tools together that work on WhatsApp on your behalf:
Tool
What it does
Example
Bot flow
When a client writes, it talks back automatically with messages, buttons and lists, then creates a task or assigns an agent.
Show a menu to anyone who types “price”, open a task for anyone who picks “Appointment”.
Meta Flow (form)
A multi-screen form the client fills in without leaving WhatsApp.
Appointment request form, sign-up form, short survey.
They also work together: one step of a bot flow sends the client a form, and the answers can be used later in the flow.
Path: Left menu → Flows
Flows screen
This feature depends on your plan. If Flows is not in the menu, it is not in your plan or you have not been given permission. See Roles and Permissions. If the page says “Flows are not ready yet”, setup is not complete; contact support.
Know this first
The 24-hour rule. After a client writes to you, you can message them freely for 24 hours. After that you can only send a template. Bot flows follow this rule. See WhatsApp Templates.
Each flow is tied to one WhatsApp line. Templates are per line too, so the template step lists only the templates of the selected line.
Bot messages show in the chat. The sender is written as 🤖 Flow name, so agents can tell which messages came from the bot.
For one client, the same flow runs only once at a time. It is not triggered again while it is in progress.
Building a bot flow
1. Create the flow
On the Flows page, click New bot flow.
Type a name in the top field and choose the WhatsApp line.
Add steps from the list on the left. Steps appear as boxes on the canvas.
Drag from the dot on the right of a box to the next box to connect them. Each exit point goes to only one place.
Click a box to open its settings in the right panel.
Click Save.
Bot flow editor
Every flow needs one trigger. It cannot be deleted and must be connected to the first step. A flow can have at most 60 steps.
2. Choose the trigger
Trigger
When does it start?
Keyword
When the client’s message contains one of the words you typed. One word per line. Letter case and Turkish characters do not matter. You can choose Contains, Exactly matches or Starts with.
Any incoming message
Every time the client writes (if they have no running flow).
First message
When the client writes to you for the first time.
Button reply
When a button in another flow is pressed. You type the button ID (buttons are numbered b1, b2, b3 in order).
Form (Meta Flow) response
When the form you choose is filled in.
CRM event
When an event happens even if the client did not write (see below).
If the triggers of several flows match the same message, the flow created first runs. Avoid using the same word in two flows.
3. Steps
Step
What it does
Text message
Sends a plain message.
Button message
Up to 3 buttons (title up to 20 characters). Each button goes to its own path.
List message
A choice list of up to 10 rows (row title up to 24, description up to 72 characters). Each row goes to its own path.
Template
Sends an approved template. The only way to reach a client outside the 24-hour window.
Media
Sends an image, video or document. The address must start with https://.
Send Meta Flow
Sends a published form to the client.
Wait
Waits for a set time or waits for the client’s reply.
Condition
Checks a variable and splits into a Yes / No path.
Set variable
Stores a value to use in later steps.
HTTP request
Sends a request to an outside system and saves the result in a variable.
Assign agent
Changes the client’s agent.
Add to group
Adds the client to a group.
Create task
Opens a task. It is assigned to the client’s agent.
Change stage
Changes the stage of the client’s latest meeting.
Hand off to human
The flow stops and the chat is left to an agent.
End
Ends the flow.
Button message, list and form steps have a Timeout exit. If you enter minutes and the client does not reply in that time, the flow continues down that path. Leave 0 to wait indefinitely.
4. Variables
You can use variables in message texts with double curly braces:
Variable
Contents
{{customer_name}}
The client’s name
{{phone}}
Phone number
{{last_reply}}
The client’s last reply (the title of the button they pressed, or the text they typed)
{{last_reply_id}}
The ID of the button or row they chose
{{flow_fieldname}}
A field from a filled-in form (example: {{flow_full_name}})
{{yourname}}
A value you made with the Set variable step
In the Condition step, write the variable name without curly braces (example: last_reply).
5. Activating
A saved flow stays inactive. Switch it on with the toggle in the Flows list. Activation can be refused because:
No WhatsApp line is selected.
The trigger is not connected to a step, or a required field of a step is empty. The message points you to the missing step.
The template in a template step cannot be used on the selected line (not approved, or not in the list).
If you edit an active flow and save it with something missing, the flow is switched off automatically. This stops a half-finished flow from reaching clients. Turn it back on when you finish editing.
Waiting and timing
Wait for time: Waits the number of minutes you enter (at least 1), then continues. If a message is sent after the wait, the client’s last message must be less than 24 hours old. If not, use a Template step.
Wait for reply: Continues when the client writes. You can use the reply as {{last_reply}}.
If a flow waiting for a reply gets no answer for 7 days, it closes on its own.
Starting from a CRM event
You can start a flow on these events even if the client did not write:
Event
When?
Meeting stage changed
When a meeting’s stage changes
New ad lead
When a new lead arrives from an ad
Quote accepted / rejected
When a quote’s status changes
These flows often start when the 24-hour window is closed. Make the first step a Template; a free-form message is rejected and the flow becomes Failed. If the client has no WhatsApp chat, the flow does not start.
Runs and errors
The Flows list shows In progress, Completed and Failed counts for each flow. The Runs button in the editor lists the last 50 runs with client name, status and error reason.
Error
Meaning and fix
outside_24h_window
24 hours have passed, so a free-form message could not be sent. Put a Template step at that point.
Template error (meta_...)
Meta rejected the template: not approved, wrong number of variables or a different line. Check its status on the Templates page.
meta_flow_not_published
The form being sent is not published. Publish the form.
loop_or_step_limit
The flow is going in circles. Add a wait or an end to break the loop.
interrupted
The server restarted while the flow was running. Write to the client by hand if needed.
If a CRM action (task, agent, group, stage) fails, the flow does not stop; the error is written to the run record.
Creating a Meta Flow (form)
1. Create a draft
Flows → Meta Flows (forms) tab → New Meta Flow (form). Choose a name, line and category, then click Create and edit. The category tells Meta the purpose (Appointment, Sign up, Contact, Survey and so on); choose the right one.
2. Design the screens
Use Add screen to open a new screen. A screen title is at most 30 characters.
Click a screen to add fields in the right panel: Heading, Text, Short answer, Long answer, Dropdown, Single choice, Multiple choice, Date, Checkbox. Order fields with ↑ ↓.
Every input field needs a label (at most 30 characters). If Field name is empty it is made from the label. Choice fields need at least one option.
Connect the screens in order by dragging from the exit point. A screen goes only to one next screen and cannot go back. The last screen with no connection completes the form and shows a Submit button.
Information entered on earlier screens is added to the result of the last screen automatically.
Meta Flow screen editor
3. Save and validate
Save and validate uploads the form to Meta and runs Meta’s check. Errors are listed in the right panel; fix them and save again. The Preview button opens the form in Meta’s preview.
4. Publish
When no errors remain, click Publish. A published form can no longer be changed. If you need a change, create a new form. A published form cannot be deleted; drafts can.
5. See the responses
You send the form to the client with the Send Meta Flow step in a bot flow. When the client fills it in, the responses show as a table with the client’s name on the page that opens when you click the response count in the Meta Flows list.
Example: appointment request
Trigger: Keyword “appointment”.
Send Meta Flow: “Please fill in the appointment form” (form: name, date, preferred time).
Create task: Title “Appointment: {{customer_name}}”.
Text message: “We received your request and will get back to you soon.”
End
You can connect the form’s Timeout exit, set to 60 minutes, to a Text message step that says “If you would like to fill in the form, write to us”.
Frequently asked questions
My flow never starts. Check that the flow is active, the right line is selected and the word appears in the message. The same flow may already be running for the client; check Runs.
The client pressed a button but the flow ended there. That button’s exit is not connected to a step; an unconnected exit counts as the end of the flow. In the editor, make sure every button and the Timeout exit are connected.
Can I write while a flow is running? Yes. Agent messages do not stop the flow. To hand the chat over completely, use the Hand off to human step.
What if I delete a flow? Its running instances are ended too; no more messages go to the client.
Do bot messages affect the “first response time” report? Yes. A bot reply counts like an agent reply.
Limits
The template step fills only the body variables. Templates with a variable in a button, or an image/document header, cannot be chosen.
Forms that fetch data and show dynamic content (server-connected) are not supported in Meta Flows.
The HTTP request step works only with https addresses and waits at most 8 seconds; local/private addresses are blocked.
If the server was down for a long time, the bot does not reply to messages older than 15 minutes.
A send error is not retried automatically; the run becomes Failed.