Native in-chat forms. Submissions land in your inbox.
Build multi-screen forms visually, publish to Meta in one click, send to any contact from the inbox or an automation. Responses arrive structured, linked to the conversation, ready to action.
No more wa.me redirects
The form opens inside WhatsApp itself. No browser switch, no drop-off, no copy-pasting OTPs back and forth.
Visual builder, not raw JSON
Drag screens, add text inputs, dropdowns, radio groups, checkboxes, date pickers. We generate the Meta-required Form wrapper and expression payload for you.
Two ways to send
From the inbox composer for one-off sends. From an automation node when a flow should trigger conditionally inside a workflow.
Submissions you can actually use
Each response carries the contact name, phone, and field values, joined to the conversation. View per-flow, export, or pipe to your CRM via httpRequest.
Visual builder, mobile preview, live republish
Three-pane editor: screens and component palette on the left, per-component config in the centre, a phone preview on the right. Save drafts as often as you like; one Publish call ships it to Meta. Same shape we use internally, so what you see is what your customers see.
- 11 component types covering most form needs
- Component-level validation: required fields, character limits, regex on text inputs
- Idempotent republish: only ships to Meta when the JSON actually changes
Best use case: EOI and lead capture
Replace your wa.me-to-Google-Form chain with a single tap. Customer gets the intro message, taps the button, fills the form inside WhatsApp, hits submit. You see the structured response in the inbox seconds later, ready for follow-up.
Frequently asked questions
What is a WhatsApp Flow?+
Meta's native in-chat form. The user taps a button on a WhatsApp message and a multi-screen form opens inside WhatsApp itself, no browser redirect. You receive the structured submission on your webhook the moment they tap Submit.
How is this different from your Automations feature?+
Automations are workflows that run on our engine, message branches, conditions, AI, HTTP calls, agent assignment, and so on. WhatsApp Flows are the structured forms Meta renders inside a WhatsApp chat. You can use both together: an Automation node can send a published Flow to a contact and resume on submission.
Do I need to write JSON or know Meta's Flow JSON spec?+
No. The visual builder lets you drag screens, add text inputs, dropdowns, radio groups, checkboxes, date pickers and a submit button. We translate the canvas into Meta's required JSON shape under the hood, including the Form wrapper and `${form.field}` payload expressions, so submissions actually carry the field values.
Can I send a Flow from the shared inbox?+
Yes. The inbox composer has a Send Flow button. Pick any published flow, set the intro message and CTA label, send. Agents can use it ad-hoc; automations can use it inside a workflow.
Where do submissions go?+
Every submission is captured on a per-flow Submissions tab in the dashboard, with the contact name, phone, and the field values they entered. You can also forward submissions to your own endpoint by chaining an httpRequest automation node after the flow send.
Are submissions linked to the contact and conversation?+
Yes. We use a flow_token to bind the submission to the contact and conversation that received it, so the response sits next to the rest of the chat history.
Your WhatsApp. Your AI. Your rules.
Join businesses automating WhatsApp without vendor lock-in.