Skip to main content
The Condition block splits a path. Evaluate contact data, then continue on the matching output.

​
What you can test

Common condition inputs:
  • Custom field — equals, contains, greater/less than, is empty
  • Tag — is present / is not present
  • Channel — WhatsApp, Instagram, Messenger, Telegram, SMS, and others
  • System properties — for example locale or last interaction, when available in the picker
Combine multiple checks with AND/OR inside the block (up to the conditions-per-block limit).

​
Build a branch

1

Collect or set data first

Conditions need something to evaluate. Capture with User Input or set a field earlier in the path.
2

Add a Condition block

Connect it after the data step. Add one rule per meaningful branch.
3

Connect each output

Wire the true/matching paths and always wire an else / default path for non-matches.
4

Test both sides

In Test Flow, force a matching and a non-matching contact state.

​
Patterns

Unconnected else-paths drop contacts into silence. Always define a fallback message, Default Reply, or handoff.

​
Limits and tips

  • Max 20 conditions per Condition block — split into sequential Condition blocks if you need more.
  • Prefer tags for coarse routing and custom fields for values.
  • Keep branch labels readable on the canvas for later audits.

​
Next

Dynamic choices

Generate options, then Condition on the selection.

Go to Flow

Hand off each branch to a specialized Flow.