Automations
How Auron turns a detected signal or a manual request into a real-world action.
An automation is a trigger plus an ordered chain of actions, built from a template and run without anyone having to drive it by hand. It's what turns "Auron noticed something" into "something actually happened" without a person as the bottleneck in between.
What triggers one
A detected signal fires an automation configured to watch for it. A schedule fires one on a timer, regardless of what happened in any given session. And a manual request lets someone ask for an automation to run, or request a new one that doesn't exist yet.
What it does once triggered
Each step in the chain is an action: updating a record, assigning an owner, sending a message, starting a downstream process. Steps that touch something real-world, an email sent, a system of record changed, can be configured to pause for a human approval before they execute instead of running unattended.
Where it's authored, where it runs
Automation templates are built in the console. Once published, an automation can be triggered, monitored and, where it pauses for a decision, approved from any surface, including the mobile app, so a run doesn't stall just because the person who needs to unblock it isn't at a desk.
Company-specific automations
Beyond what Auron ships with, an organization can build automations around its own processes and systems. See Company-Specific Automations.