The trigger: what starts the rule
A trigger is a discrete event: a lead was created, a status changed, a message arrived, a stage was reached, a timer elapsed. It fires once, at a moment in time, against one record. This matters because a rule triggered by an event will not retroactively apply to records that were already in that state before the rule existed.
The most common design mistake is confusing an event with a condition. 'Lead is unassigned' is not a trigger; it is a state. 'Lead has been unassigned for thirty minutes' is a trigger, because something has to check the clock and emit an event.
Conditions: the filter that keeps it sane
Conditions decide whether the triggered event deserves the actions. Good conditions are typed and specific — a particular pipeline, a particular assignee, a defined status list, a keyword match, a numeric threshold — because a vague condition is how a rule ends up texting a customer who called to complain.
Every condition you add reduces the blast radius. Every condition you omit widens it. Write conditions as if the rule is going to fire ten thousand times, because eventually it will.
Actions: ordered, independent, and not transactional
Actions run in order. Each one either succeeds, fails, or is skipped. What they do not do is roll back: if action three fails, actions one and two already happened. A task was created; an email left the building. There is no undo for a message a customer has already read.
That has a direct design consequence — put internal, reversible actions first and external, irreversible actions last. Create the task and update the record before you send anything outside the company.
Outcomes: eight facts people collapse into one
- Configured intent: the rule exists and is enabled.
- Trigger detection: the event was actually observed.
- Queued work: the run was created and is waiting.
- Attempted execution: the system tried to perform the action.
- Accepted request: a provider took the request from us.
- Persisted result: the outcome was written to the record.
- Verified outcome: the real-world effect was confirmed.
- Downstream side effects: other rules and notifications this one set off.