Auron
Use AuronMobile appAutomations

Triggers, actions and statuses

The labels you will see on an automation: what can start one, what its steps can do, and what its runs report.

Triggers

What starts an automation.

TriggerWhat it means
When a meeting startsThe call has connected
When a meeting endsThe call is over
When the meeting summary is readyAuron has finished summarising, so the content is available
When an entity record has no activityA record has gone quiet for long enough to be worth chasing
On a scheduleOn a clock instead of off an event
When a HubSpot contact is syncedA contact has come in from your HubSpot connection

An automation with a trigger the app does not recognise shows the trigger's raw name instead of a blank.

Actions

What an automation's steps can do. A single automation chains several of these in order. The phone describes each step in plain language under How it works.

ActionWhat it does
Get transcriptionReads what was said in the meeting
Create summaryWrites a summary of the meeting
Agentic stepAsks the agent to work through the meeting
Send emailEmails the result to an address
Get signalsCollects the signals found in the meeting
Append to CRMAdds the result to the linked record
HTTP requestSends the result to another system
WaitWaits before carrying on
Place outbound callCalls the record's phone number
Query entity recordsGathers records to look at
Get record contextReads everything known about the record
Update record fieldFills in a field on the record
Search knowledge baseLooks the answer up in a knowledge base
Save to knowledge baseFiles the result in a knowledge base
Request approvalAsks a person to approve before carrying on
Push to HubSpotWrites the record back to HubSpot, always after an approval
Post to feedPosts a card to the organization's feed and carries straight on
Organization health checkChecks what needs attention across the organization

Request approval and Push to HubSpot are the steps that involve you directly. See Approvals.

Run statuses

StatusWhat it means
QueuedAccepted, not started yet
RunningIn progress
Waiting for youPaused on an approval
WorkedFinished
Didn't finishStopped on an error
CancelledStopped deliberately
SkippedHad nothing to work on

The last four are final. A run in any of them will not change again, which is why the Activity tab stops refreshing once every run has reached one.

Skipped usually means a step had no input, such as a test run when the agent has no recent meeting to work from. It is not a failure.

On this page