Condition & Navigation Components
Opt-In
Captures user consent or agreement. Used for compliance and confirmation purposes.
Embedded Link
Displays a clickable hyperlink within text. Used to redirect users to external or policy pages.
Conditional Component
IF Condition
Displays components dynamically based on defined logic. Used to personalize flow behavior based on user input.
Footer
Displays the primary action buttons of a screen. Required to move the user to the next step in the flow.
Example Use Case
Lead Collection Flow
Scenario: A business wants to collect customer details via WhatsApp.
Workflow:
Screen 1: Heading + Name input + Phone input
Screen 2: Product selection (Image Radio Button)
Screen 3: Confirmation screen with Rich Text
Footer: Submit
Outcome: User details are collected and stored in Variables.
Common Mistakes to Avoid
Adding components on Rich Text screen
Not saving before testing
Not mapping Variables properly
Publishing without testing
Troubleshooting
Flow not publishing
Check required fields
Ensure Footer is configured
Components not showing
Check IF conditions
Verify screen structure
Rich Text not allowed
Remove other components from that screen
Inputs not saving
Confirm variable mapping
Last updated