Configuring Webhooks
Push alerts to Slack, Teams, or your own endpoint.
Webhooks are the outbound path: when something needs attention, Guardia AI posts to a URL you control.
Two kinds of destination
- Chat webhooks — Slack or Microsoft Teams incoming-webhook URLs, connected on the Integrations page. See Setting Up Slack Notifications.
- Custom endpoints — your own HTTPS URL, if you want alerts in an internal tool or SIEM. Configure it as the target of an alert rule.
What triggers a webhook
Alert rules you define on the monitoring dashboard — for example:
- a fairness metric crossing your threshold,
- data drift on a monitored model,
- a compliance-status change on a registered system,
- regulation-watch alerts.
Each rule fires to its configured destination(s) with a JSON payload describing the alert, the affected system, and a link back to the dashboard.
Good practice
- Point alerts at a channel or queue humans actually watch — an ignored webhook is compliance theatre.
- Keep the email digest on as a fallback; chat messages scroll away, the digest doesn't.
- Custom endpoints should verify the payload server-side and respond quickly (2xx) — slow endpoints get retried.