Log inStart Free Trial
Meta Tech Provider

Automation flows vs WhatsApp Flows: what each one is

WhatsApp Flows is a Meta feature for forms inside the chat: the customer taps a button and fills in structured screens, such as a sign-up, a quote request or a booking, without leaving WhatsApp. An automation flow is something else: a trigger, such as an incoming message, followed by steps that reply. They work together when automations answer messages and a Flow collects structured data.

easyCoexistence connects the WhatsApp Business number you already use to Meta's Cloud API through Coexistence and runs automation flows on it, built by asking ChatGPT or Claude or in the visual editor.

Structured interactions

How Meta describes WhatsApp Flows: a way to build structured interactions for business messaging, such as lead generation.

FLOW button

A business-initiated Flow travels as a template with a FLOW button; inside the window, as an interactive flow message.

nfm_reply

A completed Flow reaches the business's messages webhook as an interactive message of type nfm_reply, its answers in response_json.

Verified business

Meta's prerequisite for sending Flows to customers: business verification and high message quality.

10 per hour

Sending limit of a Throttled Flow, the state WhatsApp sets when a Flow's endpoint or navigation is unhealthy.

Up to 60 steps

What one easyCoexistence automation can hold after its trigger, up to 30 per line, with branches that split by rules or by your AI.

What is a WhatsApp Flow?

A form the customer fills in without leaving the chat. Meta's WhatsApp Flows let a business build screens with components such as TextInput, TextArea, Dropdown, RadioButtonsGroup, CheckboxGroup, DatePicker and OptIn, link them with navigate actions, and end with a complete action that sends the answers back. A Flow is written in Flow JSON, through Meta's Flow Builder or the Flows API. It can be static, with every screen fixed in the JSON, or call the business's own endpoint through data_exchange to fetch live data, such as available time slots, with encrypted requests. Meta's own guides use it for lead capture, pre-approved loans, insurance quotes, purchase intent and personalised offers.

What is an automation flow?

A rule that answers messages: a trigger, then steps in order. In easyCoexistence's editor it reads "When a message arrives", then "Then". The trigger picks the messages, by Every message, Has keyword, First message or After hours. The steps decide what goes back: Reply with text, Send a template, Reply with AI on your own key, Ask a question with buttons, Send a picture or file, Call my webhook or Wait, among others, up to 30 per line, with branches that split by rules or by meaning. Only one automation answers each incoming message. You build it by asking ChatGPT or Claude through the connector, which calls create_automation and test_automation, or in the visual editor. The customer sees its replies as ordinary messages from your number.

How do WhatsApp Flows and automation flows compare?

They answer different questions. A WhatsApp Flow decides what the customer fills in; an automation flow decides what the business sends back when a message arrives. One is a screen on the customer's phone, the other is logic on a server. Most businesses that use both let automations handle the conversation and keep Flows for the moment structured data is needed, such as an address, a date or a choice from a list.

WhatsApp FlowAutomation flow
What it isScreens of fields inside the chatA trigger and the steps that reply
Who starts itThe customer, by tapping a button in a messageAn incoming message that matches the trigger
Built withFlow JSON, Flow Builder or the Flows APIYour AI through MCP, or a visual editor
What comes backThe answers as JSON, in an nfm_reply messageText, a template, an AI answer or your webhook's reply
NeedsA published Flow, a verified business, a template or open windowA connected number with automations on

How is a WhatsApp Flow sent and answered?

Two ways to send it, both through the Cloud API. To start the conversation, the Flow rides on a template with a FLOW button, which Meta reviews like any template; when sending, an optional flow_token identifies the session. Within 24 hours of the customer's last message, an interactive message of type flow does the same without a template, with a call-to-action label Meta advises keeping to 30 characters. When the customer submits, an nfm_reply message arrives on the messages webhook carrying response_json. A Flow starts as Draft, sendable only for testing, becomes Published, and ends Deprecated; WhatsApp sets Throttled and then Blocked when its endpoint is unhealthy, and lifts them as it recovers.

Can automations and WhatsApp Flows work together?

Yes, with your AI or your own system doing the Flow part. The automation steps themselves do not send Flows today: the template picker lists a template with a FLOW button as one that automations cannot fill, and no step sends a Flow, though Ask a question sends reply buttons. What works:

  • Your AI: send_template passes components to Meta unchanged, so ChatGPT or Claude can send an approved Flow template to one person.
  • Your system: send a Flow message or Flow template through the Cloud API with the number's credentials.
  • A trigger for it: a keyword automation calls your webhook, your backend sends the Flow, and returns no "reply", so nothing else goes out.
  • The answers: a completed Flow reaches your Forward URL with Meta's payload, response_json included; automation steps see no text in it.

Which one do you need?

Pick by the job, not by the name, since the two words describe different layers of the same conversation:

  • Answer questions, greet new contacts or reply after hours: an automation flow.
  • Collect several fields at once, such as a delivery address or a quote request: a WhatsApp Flow, or a few Ask a question steps that save each answer to the contact.
  • Offer a few fixed choices in one tap: Ask a question with buttons, whose answer is saved in a contact field, or a reply-button or list message sent from your system, whose answers automations read as text.
  • Qualify a lead in conversation and hand hot ones to a person: an agent or a Reply with AI with instructions, plus Hand to a person or your webhook.

Common mistakes

  • Sending a Draft Flow to customers. Draft mode is for testing, WhatsApp shows a banner on it, and only a Published Flow should reach real people.
  • Expecting a Reply with AI step to read a submitted Flow. The automation receives the message without its answers; send Flow results to your system through the Forward URL.
  • Running a catch-all automation next to Flow templates. A submitted Flow still counts as a message, so the catch-all answers it; let your system or a keyword rule own those chats.
  • Editing a published Flow heavily. Edits return it to Draft, messages already sent keep the old version, and Meta suggests cloning the Flow for large changes.
Doing this with EasyCoexistence

WhatsApp Flows sit beside them: your AI can send an approved Flow template with send_template, your system can send Flows with the number's credentials, and the answers reach your Forward URL. US$ 9 down to US$ 0.75 per number per month, falling as you add numbers, with the first 3 days free.

easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.

Frequently asked questions

Do I need my own server for a WhatsApp Flow?

Not for a static one. A Flow whose screens are fixed in its Flow JSON ends with a complete action and sends the answers back as a message. An endpoint is needed only for dynamic screens that fetch data through data_exchange, such as live prices or open time slots.

Can my AI build a WhatsApp Flow?

It can help write the Flow JSON, but easyCoexistence has no tool that creates or publishes Flows. Build and publish the Flow in Meta's Flow Builder or with the Flows API, then submit a template with a FLOW button through create_template and send it with send_template.

Can I send a Flow from the WhatsApp Business app?

No. Flows go out through the Cloud API, either as a template with a FLOW button or as an interactive message, and on a Coexistence number templates are sent only through the API.

How are Flows different from reply buttons and lists?

Reply buttons and list messages give one tap to pick one option, and automations read the chosen option as text, so a keyword automation can answer it. A Flow is a set of screens with several fields, and its answers arrive as JSON for your system.

Keep reading

Ready to get started?

Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.

Start Free Trial

Verified on