Choose the right step type
A process's Steps run in order for every record. Some steps always run; outcome steps only run when the record's rule results match.
The step types
| Step | What it does |
|---|---|
| Send Email | Sends the picked Email Template for every record. |
| Send Message | Sends the picked Message Template (SMS or WhatsApp) for every record. |
| Make API Request | Makes the picked API Request for every record. |
| Rule Match Outcome | You pick a rule type in Rule Match. If any of the process's rules with that rule type matched the record, the step runs its Actions. |
| No Rule Match Outcome | Runs its Actions only when none of the process's rules matched the record. If the process has no rules, this step runs for every record. |
Actions in outcome steps
The Actions list on an outcome step can include email templates, message templates and API requests, in any mix. They run in the order listed. You can have several Rule Match Outcome steps, one per rule type, and more than one can run for the same record.
Abort Next Step
Outcome steps have an Abort Next Step switch. When it's on and the step's actions run, the record stops there and none of the later steps run for it. When the step doesn't apply to a record, the switch has no effect and the record carries on to the next step.
A common pattern is a Rule Match Outcome with Abort Next Step on, followed by a default action for everyone else.
The process Overview tab shows this as "After executing actions then do not go to next step" or "go to next step".
When a step fails
- If an action fails, the remaining actions in that step don't run. They're shown as Not executed in the record's history.
- The record is marked as failed, and no later steps run for that record.
- Other records are not affected; each record is handled separately.
Empty steps
A Send Email, Send Message or Make API Request step with nothing picked is skipped.