Automation conditions
Conditions control whether an automation continues or takes a different path based on the data involved. A condition node sits between the trigger and the actions, evaluating field values at runtime to decide which direction the chain flows.
How conditions evaluate
Each condition checks a field against a value using comparison operators: equals, does not equal, contains, is greater than, is less than, is empty, and is not empty. A condition checking "invoice amount is greater than 500" only lets the automation continue when the invoice exceeds that threshold. A condition checking "status equals Approved" blocks the chain unless the status matches exactly.
Combining conditions with AND/OR logic
Multiple conditions combine with AND or OR logic. AND requires every condition to pass before the automation continues. OR requires at least one condition to pass. A condition group checking "status equals Overdue AND amount is greater than 1000" only fires for high-value overdue invoices, while "assignee equals Sarah OR assignee equals James" fires for either team member.
Branching with conditions
Conditions create branches in the automation flow. When a condition evaluates to true, the automation follows one path of actions. When the condition evaluates to false, the automation follows a different path or stops entirely. A single automation with a "proposal status changed" trigger can branch into one set of actions for "Accepted" and a completely different set for "Declined", all within the same workflow.
Conditions evaluate at runtime
Conditions evaluate at the moment the automation runs, using live data from the triggering event, so a condition checking "project status equals Active" always reflects the project's current state rather than a stale value.
