On this page

Flow Builder is the drag-and-drop canvas where you wire together an automated WhatsApp conversation: a trigger that starts it, a chain of nodes that send messages, branch on a customer's answer, wait, call an API, or bring in a human, and edges that connect them. This article covers how to actually build and test a flow, once you already understand what a single node does; for the field-by-field reference of every node type, see the flow node reference.
Flow Builder: first 5 of 8 steps
- 1Open Flow Builder and start a flow
- 2Configure the trigger node
- 3Add steps to the canvas
- 4Connect nodes with edges
- 5Fill in each node's settings
Before you start
- Any Owner or Admin can create and edit flows by default; the permission is "Create flows," and most custom roles that include it can too.
- Flow Builder has no plan gate and no cap on the number of flows or nodes. What a plan sets elsewhere is agent seats and stored contacts; conversations are unlimited on every plan.
- Testing a flow on a real customer channel requires a connected WhatsApp number. You can build and save a draft flow without one, but the "message yourself" test step needs a live connection.
- The AI Reply node works on every plan and uses AI credits: 1,000 are free each month, and an AI reply costs 10.
- Decide your trigger before you start placing nodes. A flow with no trigger set still saves, but it never fires until you configure one; see flow triggers for the six trigger categories.
Steps
- Open Flow Builder and start a flow. From the sidebar, open Automation, then Flow Builder, type a name in the Flow name field and click New Flow. Give it a name that describes what it does rather than when you built it ("Price enquiry auto-reply" reads better six months from now than "Flow 3").

Configure the trigger node. Every new flow starts with a trigger node set to Keyword / Inbound Message. Click it and either type one or more comma-separated keywords, or leave the field blank so the flow catches any inbound message that no keyword flow claimed first. Switch the Trigger Type dropdown if you want a different trigger: Customer goes quiet, Contact enters a Segment, Contact receives a Tag, Contact field changes, Appointment Booked, Appointment Reminder, Appointment Completed, Form Submitted, or New lead arrives.
Add steps to the canvas. Click the green Add step button in the toolbar at the top left of the canvas (or press N) to open the searchable list of step types: Send Message, Send Template, CTA Button, Image Carousel, Quick Replies, Request Location, Contact Card, WhatsApp Form, Send Product, Wait for Reply, Wait until quiet, Delay, Condition, Set Variable, API Call, Action, Human Handoff, AI Agent, AI Reply (simple) and End Flow. Pick one and it appears in the middle of the screen with its settings open; drag it wherever you want it. To add the next step straight after another, click the green + under an exit that has no line yet: the step you pick is placed below, already connected. On steps with several exits (Condition, Wait for Reply and AI Agent) the + shows when you point at or select the step. Tidy up in the same toolbar lines every step up top to bottom with no overlaps (an Undo button shows for 10 seconds afterwards), and the button beside it fits the whole flow on screen. A small map of the whole flow sits at the bottom right and the zoom buttons at the bottom left.
Connect nodes with edges. Drag from the small handle at the bottom of one node to the top of the next to wire them together. A Condition node exposes two handles, labeled true and false, so you can connect a different next step to each outcome; a Quick Replies node with more than one button exposes one handle per button.
Fill in each node's settings. Click any node to open its Step settings on the right side of the screen; the X, Esc or a click on empty canvas closes them, and you can drag the panel's left edge to make it wider. Every step card on the canvas is the same width and shows two lines of its message, and the full text is in the settings. On a phone, use the Add step and Properties buttons in the bottom bar. A Send Message node needs body text; a Send Template node needs a template name, language and variable mapping; a Delay node needs a duration or a relative-to-appointment offset; an AI Reply node needs a system prompt and, optionally, a knowledge base. Use
{{name}}and{{phone}}to personalize any message with the contact's own details, or{{variable_name}}for a variable set earlier in the flow (by a Quick Replies choice, an API Call response, or a Set Variable node).Save and activate. Click Save in the editor, then click Activate on the flow's row in the Flow Builder list. Only Active flows respond to real inbound messages or events; Draft flows exist but never fire.
Test it on your own connected number. Message your own WhatsApp number with the trigger keyword (or trigger the event another way, such as booking a test appointment). There is no separate sandbox environment for flows; the live number is the test environment, so you exercise the exact node graph a real customer will run.
Watch the run counter and refine. Each flow's list entry shows how many times it has executed. Open it again to tighten a reply, add a branch, or connect a Human Handoff node once you have seen it run for real; every change applies to executions that start after you save.
A flow follows one line from each output. If you draw a second line from the same output (for example two lines from the Trigger), the builder refuses it and tells you which step the first line already leads to, and a flow that already has two lines shows a warning above the canvas. A flow with two lines, or a step connected to itself, cannot be switched on until you fix it. To send two things in a row, put the steps one after another: Trigger, then the first message, then the second.
The warning above the canvas has one button for each line that causes a problem, for example Remove the line to the first message (the one that runs) and Remove the line to the second message (never runs). Press a button to remove that line, then press Save. You do not need to find the thin line on the canvas, which helps on a tablet or phone. On a touch screen the lines, the delete cross, the connection dots and the zoom buttons are larger, and a line connects when you drop it near a dot. To connect two steps, touch the dot under the first step and drag to the dot above the second.
What you will see
An active flow with a keyword or catch-all trigger answers a matching WhatsApp message within seconds of it arriving, day or night, without anyone on your team touching a keyboard. The flow's run counter on the Flow Builder list increases by one for every execution, whether it started from your own test message or a real customer's. Inside the conversation thread, every message a flow sends is visible exactly like a message an agent sent manually, including a logged entry when a free-form node could not send because the 24-hour window was closed.
Settings and options
| Setting or field | What it does | Default |
|---|---|---|
| Flow status | Draft, Active, Paused or Archived; only Active flows respond to real triggers | Draft |
| Trigger type | Keyword / Inbound Message, Customer goes quiet, Contact enters a Segment, Contact receives a Tag, Contact field changes, Appointment Booked, Appointment Reminder, Appointment Completed, Form Submitted, or New lead arrives | Keyword / Inbound Message |
| Keywords | Comma-separated list; leave blank to catch any message no keyword flow claims first | Blank |
| Run counter | How many times the flow has started an execution | 0 |
| 24-hour window guard | Applies automatically to every free-form send node; template nodes are unaffected | Always on, not configurable |
| Opt-out and block check | Runs before every node in the graph, including on resume after a wait | Always on, not configurable |
| Version history | Not available; duplicate a flow before a risky edit to keep a fallback copy | Not saved |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Nothing happens when I message the trigger keyword | The flow is still in Draft status | Click Activate on the flow's row in the Flow Builder list |
| A step after the Trigger never runs, or the builder refused a line | Two lines were drawn from the same output, and a flow follows only the first | Press the Remove the line button in the warning above the canvas, then connect the steps one after another |
| I cannot tap or delete a line on my tablet | A line is thin and there is no Backspace key on a touch screen | Use the Remove the line buttons in the warning, or tap the line and press the red cross that appears on it |
| Two nodes seem connected but the flow skips one | The edge was dragged to the wrong handle, commonly on a Condition or Quick Replies node with several handles | Delete the edge and reconnect it from the exact labeled handle (true, false, or the specific button) |
| A scheduled message never arrives after a multi-day Delay | A free-form node hit the closed 24-hour service window and logged a failed message instead of sending | Open the conversation to confirm, then switch that step to a Send Template node, which is unaffected by the window |
| The flow ran once for a contact and never again | Only one active execution of a given flow per contact is allowed at a time; a second trigger while one is still running or waiting is a no-op | This is expected behavior; if you want repeatable triggers, check whether the earlier execution finished or is still waiting on a Wait for Reply or Delay step |
| A conversation that was waiting part-way through a flow continued differently, or stopped, after you edited the flow | Runs read the flow as it is now, so a waiting run follows your edit, and a run waiting at a step you deleted ends | Start the conversation again from your own number to test the new version; make large edits while no run is waiting |
| The AI Reply node tells the customer their message was passed to your team, and the chat shows Needs a person | No usable AI connection or no AI credits left, or the connection saved on the node has since been removed | Check the connections in Settings, then AI; VGraple AI needs no key, and the node falls back to another usable connection automatically |
Related reading
Once your nodes are in place, check flow triggers for every way a flow can start, and the flow node reference for the exact fields each node type takes. If this is your very first flow, the shorter build your first flow walkthrough covers the same ground with fewer moving parts.