Automations
Conditions
Narrow when a rule acts with grouped conditions on the trigger’s fields, match-all or match-any, and nested groups.
On this page
Conditions decide which events go on to the actions. Without any, every event that matches the trigger runs the automation.
Build conditions#
In a rule, conditions sit under Only continue when. Each clause is a field, an operator and a value:
Message text contains
invoice
Fields come from the trigger — the message text, the email subject, the task status, the site host. The panel lists what the chosen trigger carries.
Match all or any#
A group of clauses has a Match mode: every clause must be true (all), or at least one (any). A group can hold other groups, so you can write
(Email from ends with
@client.comor Email subject containsurgent) and Has attachments is true
Operators#
| Operator | Use it for |
|---|---|
| equals · does not equal | Exact values |
| contains · starts with · ends with | Text |
| greater than · greater than or equal · less than · less than or equal | Numbers and timestamps |
| is one of · is not one of | A comma-separated list of values |
| includes any · includes all | Lists, such as attachment types or mentions |
| exists · does not exist | Whether the field is present |
| is true · is false | Yes/no fields |
| matches regex | Patterns, for advanced use |
In a flow, conditions are steps: a Filter gate stops events that do not match, a Guard stops the flow unless a field exists or equals a value, and a Router or Branch selector sends events down different paths. See Actions and connectors.