Condition branches
Route contacts by saved fields, replies, or tags. One Condition node checks named branches in order and takes the first match.
On this page
First match wins
Use a Condition when different contacts need different next steps. Each named branch has its own conditions. Ravela checks the branches from top to bottom and continues down the first one that matches. It does not run every matching branch.
If none match, the contact takes Otherwise. This output is always there, so an unexpected or missing answer still has a path. You can use it to ask another question, hand off to your team, or end the flow.
This also covers a switch-style choice: check the same saved field against several values in one node instead of chaining separate Yes/No checks.
Build your branches
Add a Condition from Logic in the node palette, then select it to open its settings.
- Name the first branch after its purpose, such as Branding or Ready to book.
- Use Quick Add or Add condition to choose what to check: a saved field, a tag, a reply, or another available condition.
- For multiple conditions in one branch, choose ALL must match or ANY can match. ALL requires every check to pass; ANY requires at least one.
- Select Add branch for each additional route, up to 20 branches. Use the up and down arrows to put the most specific checks first.
- Connect every branch and Otherwise to a next step. Each branch needs at least one condition before you can publish.
Example: route by project type
Suppose Ask for Input or a Data node has saved the contact’s answer in a field named project_type. Add one Condition with three branches. In each branch, choose Saved field equals…, set Saved Field to project_type, and use equals for the comparison.
- Branding — project_type equals Branding → send your branding questions.
- Website — project_type equals Website → send your website questions.
- Consulting — project_type equals Consulting → send your booking step.
- Otherwise — ask which service they need, or send them to your team.
Order matters; names do not change connections
If two branches could match, the higher one wins. For example, put “Website AND has the VIP tag” above a general “Website” branch. Otherwise the general branch catches both groups.
Renaming or reordering a branch keeps its connections. Removing a branch asks for confirmation and removes its outgoing connection, not the downstream nodes. Review any steps left disconnected before publishing.
Older Conditions can still show Yes and No. They keep their existing connections; you do not need to rebuild them just to keep a two-way check.
Check before publishing
Use the exact saved field name from the step that writes it. Text comparisons ignore letter case. For Action buttons and Quick Replies, a payload condition compares the choice’s internal value, not its visible title.
Preview each route, including Otherwise and a case that could match more than one branch. Then test with a saved answer to check the full capture-and-route path. A Condition chooses a route; it does not change Instagram’s messaging permissions.