> ## Documentation Index > Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt > Use this file to discover all available pages before exploring further. # Webhooks > Send alert notifications to any service via customizable webhooks Webhooks allow you to send alert notifications to any service that accepts HTTP POST requests - Slack, Microsoft Teams, Discord, PagerDuty, Opsgenie, Datadog, or your own custom endpoints. ## What are Webhooks? Webhooks are HTTP endpoints that receive alert notifications when your alert rules trigger. Ankra sends a POST request with alert details to your configured URL, allowing you to integrate with virtually any notification or incident management system. Key features: * **Universal compatibility** - Works with any service accepting webhooks * **Custom payloads** - Full control over the JSON structure sent to your endpoint * **Template variables** - Dynamic values like alert name, severity, and resource details * **Pre-built templates** - Quick setup for popular services ### How Webhooks Work ```mermaid theme={null} sequenceDiagram participant Alert as Alert Rule participant Ankra as Ankra Platform participant Webhook as Webhook Endpoint participant Service as External Service Alert->>Ankra: Condition triggered Ankra->>Ankra: Apply template variables Ankra->>Webhook: HTTP POST with JSON payload Webhook->>Service: Process notification Service-->>Ankra: 200 OK ``` *** ## Home channel Set an organisation **home channel** and Ankra starts the conversation itself. Whenever something important happens - a deployment or reconcile failure, an agent going offline, a new severe CVE - and **no routing rule matches it**, Ankra posts to the home channel. It is the default destination, so your team hears about important events before anyone wires up a single rule. Connect a Slack workspace to Ankra from the **Slack integration** in your organisation settings, and invite the Ankra bot to any private channel you want to use. Open **AI** → **Settings** → **Workspaces**, find **Ankra's home**, choose a Slack channel, and save. Only **critical** and **warning** events reach the home channel; informational events stay in the in-app inbox. The home is a fallback - when a routing rule already matches an event it goes there instead, and the home is not double-notified. Alerts that already post to their own destinations are left to those destinations. *** ## Creating a Webhook Go to **Alerts → Integrations → Webhooks** and click **Create Webhook**. * **Webhook Name:** A descriptive name (e.g., "PagerDuty Production") * **Webhook URL:** The endpoint URL provided by your integration service * **Description:** Optional notes about this webhook's purpose * **Enabled:** Toggle to enable/disable the webhook For **Slack** and **Microsoft Teams** you can skip the URL entirely: once the Ankra app is installed in your Slack workspace, or the Ankra AI bot has been added to a Microsoft Teams team, the URL field is replaced by a **channel picker** and the Ankra bot posts the alerts itself. Teams channels are listed as *Team / Channel* across every team the bot is in - add the bot to a team first for its channels to appear. See [Connecting Microsoft Teams](/platform/ai-connections#connecting-microsoft-teams) for installing the bot. Choose a pre-built template for common services, or create a custom JSON payload: * **Slack** - Rich message blocks with buttons * **Microsoft Teams** - Adaptive card format * **Discord** - Embed format with fields * **Custom JSON** - Any JSON structure for other services Save the webhook, then use the **Test** button to send a sample notification and verify your configuration. *** ## Template Variables Use these variables in your custom templates. They are replaced with actual values when alerts trigger: ### Alert Information | Variable | Description | Example | | ---------------------- | ------------------------------------------ | -------------------------------- | | `{{alert_name}}` | Name of the alert | "Production Down Alert" | | `{{alert_id}}` | Unique alert identifier | "abc123-def456" | | `{{severity}}` | Alert severity level | "critical", "warning", "info" | | `{{severity_color}}` | Hex colour for severity | "#d9534f" | | `{{severity_style}}` | Adaptive Card container style for severity | "attention", "warning", "accent" | | `{{condition_type}}` | Type of condition that triggered | "resource\_state" | | `{{triggered_at}}` | Human-readable trigger time | "Dec 15, 2024, 3:45 PM" | | `{{triggered_at_iso}}` | ISO 8601 timestamp | "2024-12-15T15:45:00Z" | ### Resource Information | Variable | Description | Example | | ------------------- | ----------------------------- | ---------------------------- | | `{{resource_name}}` | Name of the affected resource | "nginx-deployment" | | `{{resource_type}}` | Type of resource | "addon", "manifest", "stack" | | `{{job_name}}` | Related job name | "deploy-nginx" | | `{{cluster_name}}` | Cluster where alert triggered | "production-us-east" | ### Action URLs | Variable | Description | | --------------------- | --------------------------------------------------------------- | | `{{alert_url}}` | Direct link to the alert in Ankra | | `{{acknowledge_url}}` | Signed one-click acknowledge link (safe to put behind a button) | | `{{dashboard_url}}` | Link to the Ankra dashboard | *** ## Integration Examples ### Slack Slack webhooks use the Block Kit format for rich messages: ```json theme={null} { "blocks": [ { "type": "header", "text": { "type": "plain_text", "text": "🚨 Alert: {{alert_name}}" } }, { "type": "section", "text": { "type": "mrkdwn", "text": "*Severity:* `{{severity}}`\n*Triggered:* {{triggered_at}}" } }, { "type": "section", "fields": [ { "type": "mrkdwn", "text": "*Resource:*\n{{resource_name}}" }, { "type": "mrkdwn", "text": "*Cluster:*\n{{cluster_name}}" } ] }, { "type": "actions", "elements": [ { "type": "button", "text": { "type": "plain_text", "text": "View Alert" }, "url": "{{alert_url}}" } ] } ] } ``` Create a Slack webhook at **Your Workspace → Apps → Incoming Webhooks**. ### Microsoft Teams Microsoft retired Office 365 Connectors, so a Teams channel no longer offers an "Incoming Webhook" — the supported route is a Power Automate (Workflows) flow using the **"Send webhook alerts to a channel"** template, which hands you an HTTP POST URL to paste into Ankra. Payloads on that route must be **Adaptive Cards** wrapped in a `message` attachment. The legacy MessageCard format is silently degraded: the flow reports success, but Teams drops every `potentialAction` button. Use `{{severity_style}}` for the card colour — Adaptive Cards cannot consume the `{{severity_color}}` hex value: ```json theme={null} { "type": "message", "attachments": [ { "contentType": "application/vnd.microsoft.card.adaptive", "contentUrl": null, "content": { "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "type": "AdaptiveCard", "version": "1.4", "msteams": { "width": "Full" }, "body": [ { "type": "Container", "style": "{{severity_style}}", "bleed": true, "items": [ { "type": "TextBlock", "text": "{{alert_name}}", "weight": "Bolder", "size": "Large", "wrap": true }, { "type": "TextBlock", "text": "Severity: {{severity}} | {{triggered_at}}", "spacing": "None", "isSubtle": true, "wrap": true } ] }, { "type": "FactSet", "facts": [ { "title": "Resource", "value": "{{resource_name}}" }, { "title": "Cluster", "value": "{{cluster_name}}" }, { "title": "Condition", "value": "{{condition_type}}" } ] } ], "actions": [ { "type": "Action.OpenUrl", "title": "View Alert", "url": "{{alert_url}}" }, { "type": "Action.OpenUrl", "title": "Acknowledge", "url": "{{acknowledge_url}}" } ] } } ] } ``` The built-in **Microsoft Teams** template in the destination form already uses this Adaptive Card format — pick the Teams preset and adjust from there. For interactive alerts inside Teams without Power Automate, connect the Ankra bot instead: see [AI Connections](/platform/ai-connections). ### Discord Discord uses the embed format: ```json theme={null} { "embeds": [ { "title": "🚨 Alert: {{alert_name}}", "description": "**Severity:** `{{severity}}`", "color": 15158332, "fields": [ { "name": "Resource", "value": "{{resource_name}}", "inline": true }, { "name": "Cluster", "value": "{{cluster_name}}", "inline": true }, { "name": "Triggered", "value": "{{triggered_at}}", "inline": false } ], "footer": { "text": "Ankra Alerts" }, "timestamp": "{{triggered_at_iso}}" } ] } ``` ### PagerDuty PagerDuty Events API v2 format: ```json theme={null} { "routing_key": "YOUR_INTEGRATION_KEY", "event_action": "trigger", "dedup_key": "{{alert_id}}", "payload": { "summary": "{{alert_name}} - {{severity}}", "severity": "{{severity}}", "source": "{{cluster_name}}", "component": "{{resource_name}}", "group": "{{resource_type}}", "class": "{{condition_type}}", "custom_details": { "resource_name": "{{resource_name}}", "resource_type": "{{resource_type}}", "cluster_name": "{{cluster_name}}", "triggered_at": "{{triggered_at}}" } }, "links": [ { "href": "{{alert_url}}", "text": "View in Ankra" } ] } ``` Use PagerDuty's Events API v2 endpoint: `https://events.pagerduty.com/v2/enqueue` ### Opsgenie Opsgenie Alert API format: ```json theme={null} { "message": "{{alert_name}}", "priority": "P1", "description": "Severity: {{severity}}\nResource: {{resource_name}}\nCluster: {{cluster_name}}", "tags": ["ankra", "{{severity}}", "{{resource_type}}"], "details": { "alert_id": "{{alert_id}}", "resource_name": "{{resource_name}}", "cluster_name": "{{cluster_name}}", "triggered_at": "{{triggered_at}}" } } ``` ### Custom/Generic For any other service, create a JSON payload that matches their expected format: ```json theme={null} { "event_type": "alert", "alert": { "id": "{{alert_id}}", "name": "{{alert_name}}", "severity": "{{severity}}", "triggered_at": "{{triggered_at_iso}}" }, "resource": { "name": "{{resource_name}}", "type": "{{resource_type}}", "cluster": "{{cluster_name}}" }, "links": { "alert": "{{alert_url}}", "dashboard": "{{dashboard_url}}" } } ``` *** ## Testing Webhooks After creating a webhook, use the **Test** button to: 1. Send a sample alert payload to your endpoint 2. Verify the message appears correctly in your target service 3. Confirm the JSON structure is valid for your integration Test payloads use placeholder values so you can see how real alerts will appear. *** ## Managing Webhooks ### Enable/Disable Toggle webhooks on or off without deleting them. Disabled webhooks won't receive any notifications but retain their configuration. ### Edit Update webhook URLs, templates, or settings at any time. Changes take effect immediately for future alerts. ### Delete Remove webhooks you no longer need. Alerts using deleted webhooks will no longer send to that destination. *** ## Managing destinations and routes from the CLI Everything above can be scripted with the `ankra` CLI, using the same personal access token as the rest of the CLI, so alert routing can live in Git and be applied from CI alongside your clusters. `-o json` and `-o yaml` keep the output parseable. ```bash theme={null} # Destinations (webhooks and bot channels) ankra alerts destinations list ankra alerts destinations create --name "Ops Slack" --url https://hooks.slack.com/services/... ankra alerts destinations create --name "Platform Teams" --type teams \ --channel-id "19:...@thread.tacv2" --teams-tenant-id ankra alerts destinations channels # channels the Ankra bot can post to (Slack and Teams) ankra alerts destinations test ankra alerts destinations update --description "On-call room" ankra alerts destinations delete # Notification routes (which notifications reach which destination) ankra alerts routes list ankra alerts routes create --destination-id --kind alert_trigger_fired --severity critical ankra alerts routes update --priority 10 --mode exclude ankra alerts routes test ankra alerts routes delete ``` Updates send only the flags you pass, so the rest of a destination or route stays untouched. The same endpoints are available directly for other tooling under `/api/v1/org/alerts/integrations` and `/api/v1/org/notifications/routes` with a bearer token. *** ## Related * [Alerts](/guides/alerts) - Configure alert rules that trigger webhook notifications * [AI Incidents](/platform/ai-incidents) - AI-powered analysis of triggered alerts *** Still have questions? [Join our Slack community](https://join.slack.com/t/ankra-community/shared_invite/zt-3a5rem8f8-cUho4epX2MoLT83bFf~VSA) and we'll help out.