Integrating follow-through

Auron deliberately stops short of being your workflow engine. It captures conversations, extracts what matters, and then either runs a bounded automation or tells your systems what happened so they can act.

Automations

An automation is a trigger plus an ordered chain of actions, created from a template in the console under Automations.

You pick a template, name it, and set its options. The steps come from the template and run in order. Triggers fire when a meeting starts, when it ends, when the summary is ready, when a record has gone quiet, or on a schedule.

The summary trigger is the useful default for anything that needs to read what was discussed, because it waits until there is something to read.

Approvals

An automation can stop and ask a person before it continues. When it does, the run pauses and an Approve or Reject card is posted to the people chosen for it.

Design for this rather than around it. An automation that drafts an email and asks before sending is adopted; one that sends and explains afterwards gets switched off. Approvals can be answered from the feed, from the automation, from the run, or from a phone. See Approvals.

Webhooks

Where the work belongs in your own systems, webhooks are the handoff. Auron tells your system that something happened and passes the context; your system decides what to do with it.

They are configured for the organization in settings, and per agent on an agent's own Webhooks tab. Use the agent level when only one agent's activity matters downstream. Failed deliveries are visible in the same place, and that is the first thing to check when a downstream system appears to have missed something.

Splitting responsibilities

Auron's side. Capture the conversation, hold the evidence, extract signals, produce summaries and reports, run bounded automations, ask for approval where a person is required, and report what happened.

Your side. Whatever needs to happen in your systems of record, on your own orchestration, under your own rules.

The split is what keeps this workable: you do not have to migrate a workflow engine to adopt Auron, and Auron does not have to model your processes to be useful.

Watching it work

Every automation run is recorded and can be opened stage by stage, showing what went in, what came out, and where it failed. An automation can be tested before it is relied on, and switched off without being deleted.

Asking for one

Automation templates are authored on the web. People on the phone can request one through a short four-question flow, which lands with your admins as a description of what is needed.