Conditional actions: If … Conditions Met
Different outcomes from one trigger — over 10,000 goes to the manager, otherwise to the rep. A conditional action branches one automation instead of making you build several.
Trigger condition versus conditional action
- A trigger condition sits at the trigger layer: fail it and the event is treated as not having happened, and nothing runs.
- A Conditional Action sits at the action layer: the event has fired, and the condition decides which actions run.
So one Data Added automation can have unconditional actions (always run) plus several conditional ones, each with its own premise.
Setting one up
In the automation editor, Conditional Action → Add Condition:
- After If, set the condition: a field, a comparator (>=, >, <, <=, =, !=, Contains, Does Not Contain) and a Parameter value, with And / Or between several. Using Formula lets you write one instead.
- After Conditions Met, hang the actions: Post to API, Submit to Table or Send Email, configured exactly as an ordinary action.
- Save the condition — an unsaved one says Save the Condition First — and then the action.
Examples
Routing new orders
- Trigger: Data Added on the order-number column
- Conditional action 1: If amount >= 10000 → Send Email to sales-manager@…
- Conditional action 2: If amount < 10000 → Send Email to the rep's email column
- Unconditional action: Submit to Table into the order log
Escalating a fault
- Trigger: Data Updated on the device-status column
- Conditional action: If status Contains "fault" And severity = "A" → Post to API into the ticketing system; otherwise just send the email
What a condition can reference
The same limit as a trigger condition: plain columns always, and a formula column only when the trigger column depends on it. Put the complicated judgement into an if formula column and have the conditional action compare only that column — clearer, and steadier.