Actions
Configuring the actions Auron can take once something is agreed.
An action is a single step Auron can execute once a conversation has produced something worth acting on: updating a record, assigning an owner, sending a message, starting a downstream process. Actions are the execution layer described in Actions; this page is about configuring which ones an organization actually has available to use.
What you configure
Actions aren't configured in isolation. They're strung together into automations, a trigger plus an ordered chain of actions built from a template. Configuring what actions exist and what an automation does with them happens on the same screen, not two separate ones.
Approvals
Any action that touches something real-world can be configured to pause for a human approval before it executes instead of running unattended. This is set at the automation level, not per action in isolation.
Where this is managed
Actions are configured as part of building an automation, in the console under Automations.