Webhooks and integrations
Telling your own systems when something happens in Auron, and connecting the services your organization uses.
Webhooks
Webhooks are how your own systems find out that something happened in Auron: a session finished, a summary is ready, a signal was detected. Instead of anyone checking the console, Auron tells your system.
They are managed through a portal inside the settings screen, where you add a destination, choose which events it should receive, and see what has been delivered. Failed deliveries are visible there too, which is the first place to look when a downstream system seems to have missed something.
Webhooks exist at two levels: for the organization here, and per agent on the agent's own Webhooks tab. Use the agent level when only one agent's activity is of interest to a downstream system.
Auron deliberately stops at telling your systems what happened. What runs next is your orchestration's business, which is why the payload carries the context rather than the platform trying to own the workflow.
Integrations
Integrations are the outside services your organization uses. There are two steps, and they belong to different people.
Enabling a service is administration. An admin turns on the integrations the organization is allowed to use.
Connecting an account is personal. Each member connects their own account to an enabled service, and can disconnect it again. This is the one item in the Organization group that members with the user role can see, because it is about their account rather than the organization's setup.
Connecting works the same way on the phone; the browser sends you to the service and back. See Integrations on mobile.