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
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.1
Connect Slack
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.
2
Pick the home channel
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
1
Navigate to Webhooks
Go to Alerts → Integrations → Webhooks and click Create Webhook.
2
Configure Basic Settings
- 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
3
Select or Create Template
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
4
Save and Test
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
Resource Information
Action URLs
Integration Examples
Slack
Slack webhooks use the Block Kit format for rich messages: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 amessage 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:
Discord
Discord uses the embed format:PagerDuty
PagerDuty Events API v2 format:Opsgenie
Opsgenie Alert API format:Custom/Generic
For any other service, create a JSON payload that matches their expected format:Testing Webhooks
After creating a webhook, use the Test button to:- Send a sample alert payload to your endpoint
- Verify the message appears correctly in your target service
- Confirm the JSON structure is valid for your integration
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 theankra 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.
/api/v1/org/alerts/integrations and /api/v1/org/notifications/routes with a bearer token.
Related
- Alerts - Configure alert rules that trigger webhook notifications
- AI Incidents - AI-powered analysis of triggered alerts
Still have questions? Join our Slack community and we’ll help out.