One workflow, multiple triggers. Automate will soon support multiple triggers per workflow, so processes that share the same steps but start from different events can live in one place, and every change you make applies to all of them.
Why this matters
Business processes are rarely started by just one event. An contract lifecycle management process, for example, might need to begin when a form is updated, a file request is initiated, or when a file is uploaded to a specific folder. Because previously a workflow could only have one trigger, teams had to duplicate the same logic for each entry point.
What you can do
- Add up to 20 triggers per workflow, as long as they belong to the same item type:
- File workflows: any file event, plus metadata events on a file
- Folder workflows: any folder event, plus metadata events on a folder
- Repeat the same trigger type with different settings. For example, add several “File Uploaded” triggers to one workflow, each watching a different folder.
- See what started a run. Run tracking highlights the trigger that fired, along with its timestamp, and shows the other triggers as not triggered.
- Upgrade existing workflows. Add more triggers to your existing Automate workflows. There's no need to rebuild them.
How to add triggers
- Select your first trigger.
- Click the (+) button below it to add another trigger or drag-and-drop one into place.
Good to know
- Trigger Variables: Downstream steps can only use variables that every trigger in the workflow provides. Adding a trigger may make some trigger-specific variables unavailable, so check your later steps after adding one. If a step already uses a variable that the new trigger doesn't provide, that reference will show as unavailable and the workflow can't be activated until it's fixed.
Availability
Multiple triggers per workflow is coming soon. More details to be added once it is generally available.