WhatsApp Flows 2026: Interactive Templates, JSON Examples & API Guide
Last verified: · Primary platform: Meta WhatsApp Cloud API v25.0+ · Meta Flows Docs ↗
WhatsApp Flows are Meta's native in-thread multi-screen form components that replace back-and-forth messaging with structured tap-through interfaces. Running on Cloud API v25.0+, static Flows render native UI elements directly inside the chat window and transmit completed responses to your webhook as JSON data.
| Flow Use Case | Interactive Screens | Meta Component Types |
|---|---|---|
| Appointment Booking | Date Picker, Time Slot, Contact Details | DatePicker, Dropdown, TextInput |
| Lead Capture | Requirement, Budget, Contact Info | RadioButtonsGroup, TextInput, Footer |
| Event RSVP | Attendance, Guest Count, Dietary Pref | CheckboxGroup, Dropdown, TextArea |
Every flow below is static: one screen, a form, a submit. No live calendar or inventory lookup: that needs a hosted Flow Data Endpoint, which is a different and much heavier commitment. A static flow is pure collection: Meta renders the UI, and the answers arrive at your webhook like any other message.
Loading the library…
WhatsApp Flows JSON Specification & Payload Limits
Building or publishing custom WhatsApp Flows requires adhering to Meta's strict component schema:
- Draft vs Published State: A draft Flow JSON can be edited and tested in Meta Flow Builder. Once published, a Flow is immutable (it can be deprecated, but never modified).
- Payload Size Constraints: Static Flow JSON screens must remain lightweight to ensure instant client rendering across low-bandwidth connections.
- Webhook Parsing: When a user completes a Flow, Meta sends a
n8n/ webhook payload containing theresponse_jsonobject cleanly mapped to screen input IDs.
How these get used
In Klaros each blueprint deploys to your WhatsApp Business Account as a draft with its JSON already uploaded. You review it in Meta's own Flow Builder and publish when you're happy. Publishing is deliberately a separate, manual step: a published Flow can be deprecated but never edited, so nothing here auto-publishes on your behalf.
Responses come back through the standard webhook and are parsed into the conversation like any other reply, so a submitted booking request or RSVP lands in your inbox as structured data rather than as a blob you have to read.
Want these on your own number? Start a free trial: the flow library is in the dashboard, and deploying one is a click. Or read the API reference if you'd rather drive it yourself.