--- title: "How do I use the Condition node in Orchestrator?" source_url: https://help.chilipiper.com/hc/en-us/articles/53527243403795-How-do-I-use-the-Condition-node-in-Orchestrator article_id: 53527243403795 updated_at: 2026-07-24T18:56:00Z content_hash: 8ac7d2b6 --- ## Who can use this feature? Available on Orchestrator Available to Admins Workspace Managers [Billing Center](https://fire.chilipiper.com/fire/admin/billing/overview) [Get a Demo](https://www.chilipiper.com/request-demo?utm_source=zendesk&utm_medium=help-center&utm_campaign=chili-hub) 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?](#what-is-the-condition-node) - [Why Use a Condition?](#why-use-a-condition) - [How a Rule Is Built](#how-a-rule-is-built) - [AND, OR, and Groups](#and-or-and-groups) - [Condition vs. Routing Rule](#condition-vs-routing-rule) - [Good to Know](#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. ![](https://help.chilipiper.com/hc/article_attachments/53569641863571) ## 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 are: `Operator`**field value** **Example** `Value`**field** is any of Company is any of: Chili Piper. Supports multiple values (comma-separated)   `comma-delimited text` is not any of Company is not any of: Chili, Piper, etc. Supports multiple values (comma-separated) `comma-delimited text` contains Company contains Chili `Text` does not contain Company does not contain Piper `Text` contains any of Company contains any of: Air  matches "Air Canada" **and** "Fairview Corp" (unintended) `comma-delimited text` contains none of Company does not contain any of: Club, Piper, etc. `comma-delimited text` starts with Company starts with C `Text` starts with any of Company starts with any of: **Air**   matches "**Air** Canada", not "Fairview Corp"  `comma-delimited text` ends with any of isolates what ends with any of: **ways** matches "Air**ways**", not "Wayside Inc"  `comma-delimited text` ends with isolate emails ending in .io `comma-delimited text` is equal to Company equals Chili Piper `Text` is not equal to Company does not equal Chili Piper `Text` is less than Revenue is less than 5   Available for certain Field Types like Number, Currency, Formula, Date, Time, Date & Time. `Number` is greater than Revenue is greater than 5 `Number` is less than or equal to Revenue is less than or equal to 5 `Number` is greater than or equal to Revenue is greater than or equal to 5 → only one numerical value `Number` is empty Check if the field has any data. Matches if not. Cannot enter any value `TextField disabled` is not empty Check if the field has any data. Matches if it does. Cannot enter any value `TextField disabled` 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.