Flow vs AI Agent
Use a Flow when you know the paths. Use an AI Agent when contacts can ask anything. Mix them with the AI Action block when you need one LLM decision inside a scripted path.
How Flows fit the product
- Build the script in Flow Builder
- Publish so other tools can use it
- Trigger it from Automation Rules, a broadcast, the inbox, a menu, or the API
- Store data on Contacts with tags and custom fields as the Flow runs
Start here
Concepts
Deterministic paths, personalization, drafts vs published, omnichannel.
Builder
Canvas tour and how blocks connect.
Build
Messages, data capture, conditions, delays, APIs, dynamic content, and JSON extract.
Operate
Test, publish, drip campaigns, triggers, and duplicates.
System fields
Built-in for contacts, ads, commerce, and more.
Common errors
Fix empty messages, messaging windows, templates, and API failures.
Quick start
1
Open Flow Builder
Go to Flows → Create New Flow and name it by purpose (for example,
Lead qualification — WhatsApp).2
Add blocks
Start with a Message, then add Quick Replies or User Input. Connect outputs with arrows.
3
Personalize
Use
{{first_name}} and your custom fields in message text. See Collect data.4
Test and publish
Click Test Flow, walk each branch, then Publish. See Test and publish.
5
Attach a trigger
Point an Automation Rule (keyword, new contact, button) at the published Flow — or send it from the inbox / API.
Related
Automation Rules
Decide when a Flow starts.
Contacts
Tags, custom fields, and segments Flows read and write.
Limits
Blocks per flow, media sizes, and condition caps.
Recipes
Proven patterns for menus, qualification, and booking.