Automation that is tried before it runs, and approved where it matters
The automation centre reacts to the platform’s typed events with recipes the workspace builds or takes from templates. A recipe can be tried in a dry run first, an action that needs it waits for approval, and every run is kept in its history.
Who uses it
- Administrator
- Manager
- Partner
What it does
- Recipes from typed triggers — the platform’s domain events — and from templates.
- Dry runs before a recipe is switched on.
- Approvals for actions that need them, decided by someone other than the person who asked.
- Run history for every recipe.
- System automations that run for every workspace.
- Limits on active automations and on external sends per day.
How it works
- Choose a trigger or a template.
- Set the conditions and actions; try it in a dry run.
- Switch it on; actions that need approval wait in the decisions inbox.
The controls that protect it
- Domain events are written in the same transaction as the change they describe.
- An automation approval is decided by someone other than the requester.
