In Flowella. Partly supported. Flowella builds Flows from a set of these components and checks the main limits before it publishes. HubSpot form fields map to the nearest component. See How HubSpot fields convert and the Flow designer. Flowella doesn’t use navigation lists, chips selectors, calendar pickers or image carousels.
Limits per screen
In Flowella. Consent checkboxes from a HubSpot form become opt-ins, so they count towards the 5. If a HubSpot form would need more than 50 components, Flowella drops its rich text blocks and keeps every question.
Text
Text can’t be empty or only spaces. Body and caption text support bold, italic, strikethrough, links and simple lists.
Inputs
Choices
Option images must be 100 KB or smaller from Flow JSON 6.0. WebP images don’t show on iOS versions before 14.
Buttons and links
Images and files
Logic
If and Switch components show or hide parts of a screen based on earlier answers, without calling an endpoint. You can nest up to three If components. A footer inside an If must appear in both branches. In Flowella, set conditions on the designer’s Logic tab.Keeping Flows readable
Limits are maximums, not targets. WhatsApp shortens long labels and option titles to fit the screen, so a label that fits on a large phone can be cut off on a small one. For practical rules, see Form design best practices.Related
Form design best practices
Labels and questions that fit.
Flows error codes
What happens when a limit is broken.
Flow JSON versions
Which version introduced what.
WhatsApp Flows overview
How Flows work.

