Agent Audit/Docs/Setup/Integrations
INTEGRATIONS · 3 MINSlack · Teams

Alert routing.

Route material events to where your security team already lives. Incoming webhooks for Slack and Microsoft Teams; SIEM webhooks (Splunk, Datadog, Sentinel) ship for Enterprise tenants in Q4 2026.

Create the webhook.

1. Create a Slack app (or use an existing one)

  1. Open api.slack.com/appsCreate New App → From scratch.
  2. App Name: Agent Audit alerts. Workspace: pick yours.
  3. On the app's home → Incoming Webhooks → Activate.
  4. Add New Webhook to Workspace.
  5. Pick the channel that should receive alerts (e.g. #soc-alerts).
  6. Slack shows a Webhook URL beginning https://hooks.slack.com/services/T…/B…/…. Copy it.
Per-channel webhooks are intentional. One webhook = one Slack channel. To split critical alerts to #soc and lower-severity ones to #noc, create two webhooks and configure two integrations in Agent Audit with different min severities.

1. Add an Incoming Webhook connector to a Teams channel

  1. Open Microsoft Teams. Right-click the channel you want alerts in → Connectors.
  2. Find Incoming WebhookConfigure.
  3. Name: Agent Audit alerts. Optionally upload an icon.
  4. Click Create. Teams shows the webhook URL.
  5. Copy the URL — it begins https://<tenant>.webhook.office.com/webhookb2/....
Connectors are being phased out in some Teams plans in favour of Workflows. If your tenant doesn't expose the classic Incoming Webhook connector, create a Workflow with the "Post to a channel when a webhook request is received" template and use the workflow URL — the payload format we send is the MessageCard schema which both connector and workflow accept.

Save in Agent Audit.

  1. Sign in to /dashboard/ as an admin.
  2. Open Settings → Integrations.
  3. Pick Kind (Slack or Microsoft Teams).
  4. Paste the webhook URL.
  5. Label: something memorable (e.g. #soc-alerts for Slack).
  6. Min severity: see the next section.
  7. Save.

Send a test message.

On the saved row, click Test. We send a test payload with severity equal to the channel's configured min severity, so the test always clears the threshold and proves the webhook is reachable.

Severity threshold.

Each channel has a min severity. Alerts below it are silently dropped. Recommended starting points:

You can change the threshold at any time on the integration row — past alerts are not re-delivered.

Troubleshooting.