.png?fit=max&auto=format&n=V5LGcGniNC1X_QJO&q=85&s=8c9ba3ce9a0d0045976180c9f669af26){kind=logo}
Conditions
Condition nodes sit between your trigger and your actions. They evaluate a value — from the trigger, a previous action, or a stored variable — against a rule you define. Based on the result, execution continues, stops, or takes a different path. Use conditions to make automations precise. Instead of notifying someone every time any task changes, add a condition to proceed only when the priority isHIGH. Instead of creating a Jira issue for every webhook, limit it to requests where the environment is production.
Two condition node types
Use Filter when you want the automation to do nothing if the condition is not met. Use IfElse when you want different actions depending on the outcome.
A branch stopped by a Filter node does not count as a failed execution. The Runs tab shows it as stopped at that node, which is correct behavior.
Operators
Expression syntax
The field you evaluate can be any value from an upstream node. Use the same variable syntax as action fields:
Example — check if a webhook came from production:
Example — check task priority:
AND / OR combinators
A single condition node can contain multiple rules. Use the combinator setting to control how they combine:
The combinator applies to all rules within the same node. To mix AND/OR logic across groups of rules, chain multiple condition nodes.
Router node — multi-way branching
The Router node extends branching to more than two paths. Define as many routes as you need, each with its own set of conditions. When the router evaluates:- The first route whose conditions pass is followed.
- Subsequent routes are not evaluated (first match wins).
- If no route matches, the default path runs (if configured).
Examples
Only proceed if task priority is HIGH — stop otherwise: Use a Filter node.Send a Slack alert for HIGH priority, log only for everything else: Use an IfElse node.
- True path → Slack: Send Message
- False path → Data Store: Log event
Only proceed if a webhook is from production and has a version set: Use a Filter node with All conditions (AND).
Route a task by priority across three outcomes: Use a Router node with three routes as shown in the table above.