How triggers, conditions, and actions work
The shape of an automation rule — when it runs, what has to be true, and what it does.
An automation rule has three parts:
- Trigger — the one event that makes the rule run. See the trigger reference.
- Conditions — zero or more checks against that event's data; all of them have to match. See the condition reference.
- Actions — one or more things the rule does, in order, once conditions pass. See the action reference.
Creating a rule
- Go to Automation and click New rule.
- Name it, and pick a When trigger.
- Configure the first action inline.
- Click Create rule — conditions, and additional actions, can only be added after the rule exists.
- Open the rule to add conditions ("Add condition") and further actions ("Add action"), reorder actions with the up/down arrows, and toggle Enabled.
- Click Save.
What "no conditions" means
A rule with zero conditions runs on every event of its trigger type — conditions are purely a filter, not a requirement. Conditions are AND-only: every condition has to match, and there's no OR or nested grouping. If you need "either A or B", that's two separate rules with the same actions.
Checking what happened
Each rule's page has a Recent runs list — every time the rule fired, its status
(SUCCESS, PARTIAL_FAILURE, FAILED), when, and (expandable) which individual
actions succeeded or failed and why. A PARTIAL_FAILURE means some actions in the rule
succeeded and others didn't — actions run independently, so one failing doesn't stop
the rest from attempting to run.
Last updated on