Flows
Journeys, not chat parsing.
Multi-step, phone-native journeys: forms, pickers, confirmations, rendered by WhatsApp itself. You get structured data back instead of free text.
Flows: journeys, not chat parsing.
Multi-step, phone-only journeys, forms, pickers, confirmations, rendered natively by WhatsApp. Chain the screens in the console's editor and wire each step to your endpoints.
You get structured data back instead of free-text replies to parse.
Pick a slot that works, takes 30 seconds.
Book an appointmentStep 1 of 3
Full name
Marina Costa
Preferred time
Tomorrow · 14:00
Continue
Runs in a native sheet inside WhatsApp on the phone.
How it works
Building a Flow.
Design it once; WhatsApp renders it natively on the phone.
1
Design the screensForms, pickers, and confirmations in the console's editor.
2
Wire each stepEvery screen posts to your endpoint; branch on the answers.
3
Collect structured dataA completed journey returns typed JSON, not a chat transcript.
By the numbers
The journey surface.
What a Flow can ask and return.
Surfacenative sheet, phone-only
Inputsforms · pickers · confirmations
Stepsmulti-screen with branching
Outputstructured JSON
Publishingfrom the console
Ship a WhatsApp integration this afternoon.
Free on the sandbox. No credit card. The projects you start here migrate straight into production.