Integrations

Email Alerts

Email alerts are enabled by default. When a source is classified as FAILURE or MISSING, CanaryAlert sends an alert to your account email.

You can configure a separate alert email address in Settings if you want alerts to go to a different address (e.g., a shared inbox or on-call email).

Slack

Send alert notifications directly to a Slack channel using incoming webhooks. Configure your Slack webhook URL in Settings.

Setup

1. 1. Go to your Slack workspace settings and create an Incoming Webhook for the channel where you want alerts
2. 2. Copy the webhook URL (it looks like https://hooks.slack.com/services/T.../B.../...)
3. 3. Go to CanaryAlert Settings and paste the URL in the Slack Webhook URL field
4. 4. Click Save — alerts will now appear in your Slack channel

Custom Webhooks

Send alert data to any HTTPS endpoint. Use this to integrate with PagerDuty, OpsGenie, Microsoft Teams, or your own systems. Configure webhooks in Settings.

Retry logic

Failed webhook deliveries are automatically retried up to 3 times with exponential backoff. HTTP 2xx is treated as success; HTTP 4xx/5xx, network errors, and timeouts (5s per attempt) trigger a retry.

Webhook failures never block email or Slack alerts. Each attempt is logged in CloudWatch.

Custom headers

Add up to 5 custom HTTP headers to every webhook request. Use this for authentication tokens, routing keys, or any headers your endpoint requires. Header values are masked in the UI and never logged.

Authorization: Bearer pd-your-token-here
X-Routing-Key: your-routing-key

Payload templates

Choose from preset templates or define a custom JSON format. Available templates:

Template variables

Custom templates support these placeholders:

{{event}}           — always "alert"
{{source_id}}       — source ULID
{{source_name}}     — human-readable name
{{classification}}  — SUCCESS / FAILURE / WARNING / MISSING
{{confidence}}      — 0.0–1.0
{{reasoning}}       — AI explanation
{{timestamp}}       — ISO 8601
{{dashboard_url}}   — link to source detail page

Default payload format

The default template sends this JSON payload on every alert:

{
  "event": "alert",
  "source_id": "abc123def4",
  "source_name": "Veeam Nightly Backup",
  "classification": "FAILURE",
  "confidence": 0.95,
  "reasoning": "Email indicates backup failure...",
  "timestamp": "2026-02-18T03:45:00Z",
  "dashboard_url": "https://canaryalert.io/dashboard/sources/abc123def4"
}

PagerDuty setup

1. 1. In PagerDuty, create an Events API v2 integration on your service and copy the Integration Key (routing key)
2. 2. In CanaryAlert Settings, set your webhook URL to https://events.pagerduty.com/v2/enqueue
3. 3. Add a custom header: X-Routing-Key with your integration key as the value
4. 4. Select the PagerDuty Events v2 payload template
5. 5. Click Save Webhook Settings — FAILURE and WARNING alerts will now create PagerDuty incidents, and SUCCESS will auto-resolve them

Microsoft Teams setup

1. 1. In Teams, go to the channel where you want alerts → Connectors → Incoming Webhook → Create
2. 2. Copy the webhook URL
3. 3. In CanaryAlert Settings, paste the URL and select the Microsoft Teams payload template
4. 4. Click Save Webhook Settings — alerts will appear as Adaptive Cards in your Teams channel

Digest Notifications

Get a daily or weekly email summary of all your source statuses. Digests include a status overview, any active issues, and recent event highlights. Configure your digest schedule in Settings.

See Digest Notifications for full setup instructions.

REST API

A full REST API is planned for programmatic access to your sources, events, and configuration. This will enable custom dashboards, mobile apps, and third-party integrations.