Condition checks a test and either runs a set of steps or skips them, then continues the automation. It is the simplest control-flow node: one conditional path (the True branch) and a default behavior of carrying on when the test fails. Use Condition for a simple "only-if" insert — run these extra steps only when this is true, then carry on either way.
Overview
The Condition (If / Else) node checks a condition and controls what steps execute next. When the condition is true, the run follows the node's If / True branch and executes the steps you placed there. When it is false, that branch is skipped and the run continues to whatever comes after the Condition node — false is not a dead end.
You build the test from data pills and comparison operators (equals, greater than, contains, is empty, and so on), and you can combine several checks with and / or.
Note: By default, the True branch contains a blank node. You can delete it if needed, but the branch must contain at least one node.
Condition vs. Branch
Use Condition for a simple "only-if" insert: run these extra steps when a test passes, then carry on either way. Use Branch when each outcome needs its own distinct set of steps — for example, routing a ticket differently for "approved", "rejected", and "needs info" all in one node. If you need to act differently in the false case, either place those steps after the Condition (they run whenever the True branch did not), or switch to a Branch node.
Operations Supported
Operator | Description |
|---|---|
Equals to | Checks if field value is exactly equal to specified value |
Does not equal | Checks if field value is not equal to specified value |
Contains | Checks if field value contains specified substring |
Does not contain | Checks if field value does not contain specified substring |
Match Regex | Checks if field value matches specified regular expression pattern |
Does not match regex | Checks if field value does not match specified regex pattern |
Starts with | Checks if field value begins with specified substring |
Ends with | Checks if field value ends with specified substring |
Less than | Checks if field value is less than specified value |
Less than or equal to | Checks if field value is less than or equal to specified value |
Greater than | Checks if field value is greater than specified value |
Greater than or equal to | Checks if field value is greater than or equal to specified value |
Is present | Checks if field value is present (not null or empty) |
Is not present | Checks if field value is not present (null or empty) |
Use Case
Example: Receiving a Slack notification for high-priority Zendesk tickets only.
Set a condition comparing the 'priority' field using the "equals to" operator with "high" to identify high-priority tickets.
In the True branch, select Slack and choose the "Post Message" action to notify your team.
For non-high-priority tickets, the Condition is false — the True branch is skipped and the run continues past the node. Add a Stop node after the Condition if you want to terminate the run for non-matching items.
Input Features
Flexible Conditions: Define criteria based on text, numbers, dates, boolean values, and other data types.
Conditional Operators: When grouping two conditions, use AND to require both conditions for a true result, or OR to require only one condition for a true result.
Grouping: Combine multiple conditions for complex logic including both OR and AND operators. For example: when a ticket is created in Zendesk, if priority is "High" AND status is either "Open" OR "Awaiting Assignment", send an email to the support team.
Deletion: Use the delete button to remove any condition or group of conditions.
Cloning: Use the clone button to duplicate any condition or group without manually re-entering them.
Filtering: Filter specific variables in the condition node for filtered results.
Nested Conditions: Create hierarchies of conditions within nodes for diverse automation scenarios.
Output Parameters
The output of a Condition node is a boolean — true or false. When true, the steps in the True branch execute. When false, the True branch is skipped and the run continues to the next node after the Condition.
Notes
Keep the following in mind when using the Condition node.
The Condition node has one conditional path — the True branch. There is no separate False / No branch; when the test fails, the run simply continues past the node.
Steps placed after the Condition node run regardless of the test result — use this to share cleanup or notification logic across both outcomes.
To act differently when the condition is false, either place those steps after the Condition (they run when the True branch didn't fire) or switch to a Branch node with labeled paths for each outcome.
You can combine multiple checks within a single Condition using AND and OR logic, and nest groups for more complex rules.
Use Condition for a simple "only-if" gate; use Branch when three or more distinct outcome sequences are needed.
If you find yourself chaining several Condition nodes to handle multiple outcomes, consider consolidating them into a single Branch node for clarity.