Triggers, actions and statuses
The full set of labels you will see on an automation: what can start one, what it can do, and what its runs report.
Triggers
What starts an automation.
| Trigger | What it means |
|---|---|
| When a meeting starts | The call has connected |
| When a meeting ends | The call is over |
| When the meeting summary is ready | Auron has finished summarising, so the content is available |
| When an entity record has no activity | A record has gone quiet for long enough to be worth chasing |
| On a schedule | On a clock rather than off an event |
An automation built on a trigger the app does not recognise shows the raw trigger name rather than a blank row, so an unfamiliar one is visible instead of hidden.
Actions
What an automation can do. A single automation chains several of these in order.
| Action | What it does |
|---|---|
| Get transcription | Fetches the transcript of the session |
| Create summary | Writes a summary |
| Agentic step | Runs an agent over the material with its own instructions |
| Send email | Emails the result |
| Get signals | Collects the signals detected in the session |
| Append to CRM | Writes into your CRM |
| HTTP request | Calls another system |
| Wait | Pauses for a set time before continuing |
| Place outbound call | Rings someone |
| Query entity records | Looks up records matching a condition |
| Get record context | Reads what is known about a record |
| Update record field | Writes a value back onto a record |
| Search knowledge base | Looks something up in a knowledge store |
| Save to knowledge base | Files something into a knowledge store |
| Request approval | Stops and asks a person, then continues or does not |
Request approval is the one that involves you directly. See Approvals.
Run statuses
| Status | What it means |
|---|---|
| Queued | Accepted, not started yet |
| Running | In progress |
| Waiting for you | Paused on an approval |
| Success | Finished |
| Failed | Stopped on an error |
| Cancelled | Stopped deliberately |
| Not run | Skipped, usually because it had nothing to work on |
The last four are final. A run in any of them will not change again, which is why the Runs tab stops refreshing once every run has reached one.
Not run is worth understanding: it usually means a step had no input, such as an automation run on demand when the agent has no recent meeting to work from.