Automations
Triggers and actions that run around your sessions, built from templates, with approvals and a run history.
An automation is what happens around a session without anyone doing it. A trigger fires, a set of actions runs. The empty state puts it plainly: automate what happens around your meetings.
Creating one
Automations are built from templates rather than from a blank canvas. You pick a template, and then:
- Name it. The template's name is offered as a default.
- Set its options. The parameters the template exposes, which is where you decide the specifics for your organization.
- Review the steps. The trigger and actions are shown in order. They come from the template and cannot be rearranged.
Which templates are available depends on what is enabled for your organization. If a template you need does not exist, you can request one.
Triggers
| Trigger | When it fires |
|---|---|
| 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 chase |
| On a schedule | On a clock rather than off an event |
The summary trigger is the useful default for anything that needs to read what was discussed, since it waits until there is something to read. The inactivity trigger is the one that generates work rather than reacting to it.
Actions
An automation chains actions in order. The set covers reading a session (get the transcript, create a summary, get the signals), working with records and knowledge (query records, get record context, update a record field, search or save to a knowledge store), reaching outside (send an email, append to CRM, make an HTTP request, place an outbound call), and control (wait, run an agentic step, request approval).
The full list with plain-language labels is in the mobile reference, which shows the same actions as they appear to whoever is reading a run.
Approvals
An automation can pause and ask a person before it continues. When it does, it posts a card into the feed with Approve and Reject, and there is a list of pending approvals so nothing sits unnoticed. Once resolved the card records the outcome, and an approval left too long expires.
Approvals can be resolved from the console, from the feed, or from the phone, since an automation waiting on a decision should not need someone at a desk.
Testing and runs
An automation can be tested before it is relied on. Every run is recorded, and each run can be opened to see what happened, which is where to look when something did not fire as expected.
Switching them off
Automations have an enabled state, so one can be turned off without being deleted. The sessions that would have triggered it simply do not.
Where they show up
An agent's automations are listed inside every session that agent runs, including on the phone, so whoever is in the meeting can see what is going to happen around it. See Automations on mobile.