Who can use this feature?
In this article, we will learn more about the Condition node and how to set it up in Ochestrator, ensuring your Flows branch intelligently and route each prospect or account smoothly.
Table of Contents
- What Is the Condition Node?
- Why Use a Condition?
- How a Rule Is Built
- AND, OR, and Groups
- Condition vs. Routing Rule
- Good to Know
What Is the Condition Node?
The Condition node creates an if/then branch: a TRUE path and a FALSE path, based on a rule you define.
For example, "If the Account has more than 800 employees, take the Enterprise path. Otherwise, everyone else." Enterprise gets a leadership alert; everyone else gets a lighter touch.
[Screenshot: Condition node example with Enterprise vs. everyone-else branch]
Why Use a Condition?
A Condition keeps Flows focused. Instead of one action firing for everyone and sorting it out later, the Flow branches and treats the right accounts the right way.
A Condition reads from any data available so far: fields from the Trigger, or CRM data from a Matching node. The usual pairing is Matching first, Condition second; the Condition can only branch on what an earlier node put on the table.
How a Rule Is Built
A rule has a left side (the field), an operator, and usually a right side (the value to compare against).
Operators available: is equal to / is not equal to; contains / does not contain; is any of / is not any of; contains any of / contains none of; starts with / ends with (plus "any of" versions); greater than / less than (>, <, >=, <=); and empty / not empty, for "is there anything here at all."
The right side can be a static value typed in, or another variable from the Flow, so two fields can be compared against each other.
Example: Type is equal to "Prospect" AND Number of Employees is greater than 800.
AND, OR, and Groups
Multiple rules can be combined. AND means every rule has to be true; OR means any one is enough. Groups can also be nested, so "(A AND B) OR C" is fair game.
💡 Tip: Reach for groups the moment a flat list of ANDs starts lying about what you mean. "(Enterprise AND Prospect) OR (Existing Customer)" says it clearly. A single row of ANDs cannot.
Condition vs. Routing Rule
This is the one people mix up. A Condition is built inline, for this one Flow. A Routing Rule reuses logic already saved in Chili Piper, across many Flows. For a one-off branch that only matters here, use a Condition. For a check that keeps getting rebuilt Flow after Flow, that is a Routing Rule.
Good to Know
💡 Tip: A condition can also be used on a Trigger, so the Flow only runs when the event matches. Use that to keep noise out entirely, and a Condition node inside the Flow to branch once inside.
- Conditions do not handle arrays or multi-value fields; if a field holds a list of values, branching reliably across all of them is not yet supported;
- Some fields offer a picklist, such as Product within a meeting, which allows picking the specific products a meeting was booked through; this is not yet available for all picklists, for example Meeting Types or Routing Rules/Flows.
Comments
0 comments
Please sign in to leave a comment.