Build a form that lives inside WhatsApp.
The Flowella Flow builder puts a WhatsApp Flow together on a blank canvas, with a live phone preview. Add fields and screens, decide which questions show and which screen comes next, then publish. No HubSpot form, no developer, and every answer comes back as structured data.
- Start from
- A blank canvas, no code
- Field types
- 11, from text to photo uploads
- Logic
- Show, hide and branch
- Answers go to
- Flowella, CSV or your webhook
One answer picks the next screen.
This is screen routing, built in the Routing tab. A conditional branch sends people to a different screen depending on what they picked, a fallback catches everyone else, and each path ends on its own screen. Back in WhatsApp follows the path they took, with their answers kept. Try it: choose car, home or pet, and screen 2 changes to match.
- You send a message with a button
- They tap it, and the form opens over the chat
- Screen 1 asks what to insure
- Screen 2 follows the answerCar detailsHome detailsPet details
- Screen 3 books the call
- They submit, still inside WhatsApp
Today
Tap Get a quote to open the Flow. Your first answer decides the second screen.
Tap Get a quote. Your first answer picks screen 2.
Everything a real form needs.
Six tabs: Build, Logic, Routing, Versions, Submissions and Settings.
-
Eleven field types
Short answer, paragraph, email, phone, number, dropdown, single and multiple choice, date, photo or document upload, and opt-in. Set the label, help text, whether it’s required, and validation for emails, phone numbers and web addresses.
-
Questions that show up when they matter
A rule shows or hides fields based on an earlier answer, such as asking for a policy number only when someone says they’re a customer. The phone preview follows the same rules.
-
Branches that always end well
Send each answer to the right screen, and give every path its own ending and completion message. If a screen can’t be reached or a path never ends, the builder lists it and won’t publish until it’s fixed.
-
Checked before Meta sees it
Each screen holds up to 50 components, Meta’s limit, and the builder warns you as you get close. If WhatsApp rejects a Flow, you see which screen and component to fix, and the live version stays as it was.
-
Versions you can trust
Every publish is a new version that never changes. A template keeps opening the version it was built with, each submission is kept against the version the contact completed, and field IDs are never reused.
-
Answers where you need them
Every submission is stored in Flowella and can be exported as CSV or sent to your own systems by webhook. On HubSpot, sync a form instead, and the answers land on the contact record.
From blank canvas to sent, in three steps.
You need a WhatsApp number connected to Flowella, and an approved template with a Flow button to send it.
-
1
Step 1: Build it
On the Flows page, select New Flow, give it a name and build: drag in fields, add screens, then set the logic and routing.
The Flow builder guideNew FlowSample data- Flow name
- Contact request
- WhatsApp number
- +44 20 7946 0999
- Screens
- 3
-
2
Step 2: Publish a version
Save drafts as you go, then publish. Each publish becomes a new version on WhatsApp, and a failed publish never touches the live one.
VersionsSample data- v2
- Live
- v1
- Retired
- Routing
- No issues
-
3
Step 3: Send it
Add the Flow to a template’s button and get it approved. Send it from a bulk send, the inbox, a HubSpot workflow or the API, and watch the submissions arrive.
Send it in bulkContact requestSample data- Template
- Approved, with a Flow button
- Submissions
- 128
- Webhook
- Delivering
In our customers’ words.
Exceptional engagement platform that transformed our student conversion with 160% increase in same-day applications and 90% WhatsApp response rates.
Peter HudsonDirector of Admissions, Brand & Customer Innovation
Game-changing donation campaign tool that delivers personal WhatsApp engagement with seamless automation and dramatically better completion rates.
Lawrence Tribe-EndtCommercial Director, Countryside Alliance
Straight answers.
The questions people ask before they build their first Flow. The full guide is in the knowledge base: Build a WhatsApp Flow in the Flowella designer.
Form design tips for FlowsBuilding
Do I need HubSpot?
No. The Flow builder works with Flowella on its own and a connected WhatsApp number. If you do use HubSpot forms, you can sync one into a Flow instead, and the answers go back to HubSpot.
How many screens can a Flow have?
As many as the form needs. Each screen holds up to 50 components, which is Meta’s limit, and the builder warns you before you reach it. However many screens a Flow has, sending it counts as one billable message.
How do show and hide rules work?
Rules on the Logic tab show or hide fields based on an earlier answer. If someone answers a field and a later answer hides it, Flowella still keeps and submits that answer.
What happens when I change a published Flow?
Publish again. Each publish is a new version, and published versions can’t be edited. A template keeps opening the version it was built with, so nobody sees a Flow change halfway through a campaign. To send the new version, update the template’s Flow button.
Sending and answers
How do I send a Flow?
Through an approved template with a Flow button. Create the template, choose the Flow, get it approved, then send it from a bulk send, the inbox, a HubSpot workflow or the API.
Where do the answers go?
Every submission appears on the Flow’s Submissions tab, against the version the contact completed, with retired versions shown under the labels they had then. Export them as CSV, or send each one to one of your webhooks as it arrives.
Will my integration break when I edit the form?
Yes. Each field has a permanent ID that never changes and is never reused, so your exports and webhook integrations keep working as the form changes.
Build your first Flow today.
Start on a blank canvas, publish it to WhatsApp and send it to your list. Free 14-day trial, no card for Flowella.
Book a Flowella demo · 30 minutes on Teams