Create an automation that only another automation can start
The trigger Another workflow starts it turns the automation into a reusable part. It never runs on its own, only through the Start another workflow step.
Before you start · for owners and managersPermission to edit workflows
- You need: Permission to edit workflows
Steps
How it works
It runs on the calling automation’s record, so it works from any unit.
It receives the old and new value from the caller, and the fields of its message or email if the caller started with a message or an email. These fields show in conditions and variables.
Its own conditions always apply; if they aren’t met, the run is skipped.
Each of its runs has its own entry in Follow the run log, and retry or resume from the failed step, with the name of the automation that called it, and counts as a separate execution.
If it’s paused, the call is skipped and the calling automation carries on with its steps.
If something goes wrong
A real example
The “escalate to the manager” steps were repeated in 4 automations.
- An “Escalation” automation with the trigger Another workflow starts it: notify the manager, create an urgent task, and add a comment.
- The four automations call it with a single action.
Escalation is now changed in one place instead of four.