Automation conditions
Conditions control whether an automation continues or takes a different path based on the data involved. A condition 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 one or more fields on a record against expected values. A condition checking "invoice status equals Paid" only lets the automation continue when the status matches exactly. A condition checking "task assignee equals Sarah" blocks the chain unless the assignee matches. Multiple field checks within a single condition all use AND logic, meaning every check must pass for the condition to evaluate as true.
Combining multiple checks
A single condition can check multiple fields at once. All checks within the condition must pass (AND logic) for the condition to evaluate as true. A condition checking "status equals Overdue" and "assignee equals Sarah" only continues when both match. To handle different scenarios, separate conditions can branch the automation into different paths, with each branch running its own set of actions.
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 event that started the automation, so a condition checking "project status equals Active" always reflects the project's current state rather than a stale value.
