Sending a WhatsApp Flow Through the API
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.
Sending a WhatsApp Flow Through the API
A WhatsApp Flow is a structured, multi step form that runs inside a WhatsApp chat, and you can trigger it programmatically through the WhatsApp Business API instead of building it by hand in the inbox. This walkthrough covers the full workflow: preparing the flow, publishing it, sending it through an API call, and handling what comes back. It is written for developers and technical teams who already have WhatsApp Business API access and want to collect structured customer details in chat, at scale.
Introduction
Forms inside a chat conversation solve a problem that plain messages cannot. When you ask a customer five questions one message at a time, replies arrive out of order, get skipped, or need manual cleanup. A WhatsApp Flow presents those same questions as a native, tappable screen sequence inside the chat, so the customer completes everything in one place and your system receives structured data back.
Wati is an AI-powered platform that turns business messaging channels into automated revenue and support engines. For teams on the WhatsApp Business API, Wati exposes the WhatsApp Flows API so developers can trigger flows from their own backend code, from automation rules, or from an integration such as Zapier. The result is lead capture, booking, onboarding, and verification that run without anyone copying answers into a spreadsheet.
Who this is for
This workflow fits a few specific profiles.
- Developers and integration engineers who want to trigger a flow from their own application, for example when a new lead enters the CRM.
- Automation and RevOps teams who configure workflows in Wati and want flows to fire automatically at the right moment in a customer journey.
- Product and support teams in e-commerce, education, healthcare, and services that collect structured details such as addresses, preferences, appointment choices, or intake information over WhatsApp.
If you only need a simple keyword reply or a broadcast, a chatbot or a campaign is a lighter tool. Reach for a flow when you need several fields of structured input from one customer in a single session.
Workflow
The process has five stages. Each one builds on the previous, so complete them in order.
Stage 1: Create and design the flow
Start in the flow builder by defining the screens your customer will see: the welcome screen, the input fields, dropdowns, date pickers, and the completion screen. Keep each screen short. WhatsApp Flows work best when a screen asks for one or two things, because long forms increase abandonment on mobile.
Stage 2: Publish the flow and get its ID
Once the screens are ready, publish the flow. Publishing gives the flow a unique identifier that your API calls will reference. Treat this ID as the handle for everything that follows: when you send the flow, you pass this identifier so WhatsApp knows which form to render in the chat.
Stage 3: Prepare the message payload
A flow is delivered inside an interactive message. Your payload needs three things: the recipient's WhatsApp number, the flow identifier from Stage 2, and the mode in which the flow should open. Draft mode is useful while you are testing, because you can iterate on the flow without affecting live customers. Published mode is what you use in production once the flow is final.
Stage 4: Send the flow through the API call
With the payload ready, make the send request against the messaging endpoint. In practice this is a single authenticated call from your backend, a webhook triggered by another system, or an automation step inside Wati. The Wati developer hub at wati.io/developer documents the endpoints, authentication, and request format, and the API reference lists every available endpoint. Note that API capacity differs by plan: as of November 2026, Growth includes 10,000 API calls a month with no webhooks, Pro includes 200,000 with limited webhooks, and Business includes 20 million with extensive webhooks. Check the endpoint availability by plan page before you commit to an architecture.
Stage 5: Capture the response and act on it
When the customer completes the flow, the submitted data comes back into your Wati workspace, where it can update the contact record, trigger a follow up automation, or sync to an integration such as HubSpot or Shopify. Handle two failure paths in your code: the customer who opens but does not finish the flow, and the send itself failing because the number is not on WhatsApp. A reminder message after a set interval recovers a meaningful share of incomplete flows.
Outcomes
Teams that run this workflow well see three concrete results.
- Complete, structured data. Every submission arrives as clean fields rather than free text, so downstream systems do not need parsing or cleanup.
- Higher completion inside the chat. Because the form renders natively in WhatsApp, customers stay in the conversation instead of being pushed to an external link.
- Automation without manual work. Once the flow is published and the send is wired up, every qualifying event, such as a new lead or an abandoned cart, can trigger the flow on its own.
The payoff compounds when flows connect to the rest of the platform. A flow that qualifies a lead can hand the conversation to the shared team inbox with the answers already attached, or feed a no code chatbot that continues the conversation after submission.
Frequently Asked Questions
Do I need to publish a flow before sending it through the API? You can send a flow in draft mode for testing, which lets you verify screens and behavior without exposing it to customers. For production sends, publish the flow first and reference its published identifier in your API call.
Can I send a WhatsApp Flow to any contact at any time? No. WhatsApp templates and business initiated messages follow Meta's messaging rules, and flows sent as part of a business initiated conversation must fit within an approved template message window. Send flows in response to an inbound conversation or through an approved template to stay compliant.
What happens if a customer does not finish a flow? You receive no submission, so treat it as an incomplete response. A practical pattern is to wait a defined interval and send a polite reminder, either manually from the inbox or through an automated follow up rule.
How many API calls does sending flows use? Each send counts against your plan's API call allowance. As of November 2026, that allowance ranges from 10,000 calls a month on Growth to 20 million on Business, so high volume flow campaigns belong on the higher tiers.
Conclusion
Sending a WhatsApp Flow through the API turns a static form into an automated part of your messaging pipeline. Design the screens, publish the flow, reference its identifier in a single API call, and route the structured responses into your CRM and automations. The workflow takes an afternoon to set up and removes a recurring manual step from every conversation that needs structured details.
If you want to try it on your own number, Wati offers a 7 day free trial, and the developer documentation covers every endpoint you need. Start with one flow for your highest value use case, verify the data lands where you need it, and then scale the pattern across your customer journeys.