Notification channels

A channel is a destination for alert events. Each alert rule has one primary channel and can add up to 20 more, all delivered to in parallel when the rule fires; the same channel can be reused across many rules. Manage channels at imaa.w3i.io/settings/notifications.

Channel types

Each channel has a type and a JSON config blob. The shape ofconfig depends on the type:

email

{
  "email": "you@example.com"
}

slack_webhook

{
  "webhook_url": "https://hooks.slack.com/services/T000/B000/XXXX"
}

Use a Slack incoming webhook URL. Create one in your Slack workspace under Apps → Incoming Webhooks.

sms

{
  "phone_number": "+15551234"
}

E.164 format. SMS deliveries count against your monthly alert quota.

webhook

{
  "url": "https://your.api/imaa-hook",
  "secret": "optional-shared-secret"
}

If secret is present, IMAA HMAC-signs every request. See Webhook signatures for the exact scheme, headers, and verification code.

discord

{
  "webhook_url": "https://discord.com/api/webhooks/XXXX/YYYY"
}

Use a Discord channel webhook. Create one under Server Settings → Integrations → Webhooks. Alerts arrive as Discord embeds with a severity-coloured side stripe matching the rule's severity — critical red, warning amber, info blue.

pagerduty

{
  "routing_key": "your-pagerduty-routing-key"
}

Uses the PagerDuty Events API v2. Create a service in PagerDuty with integration type Events API v2 and paste the routing key here. Every alert routed to this channel triggers a PagerDuty event (event_action: trigger) carrying the rule's severity (info/warning/critical map 1:1 onto PagerDuty severities), deduplicated by a hash of the alert subject so repeats of the same alert group into one incident. Whether an event pages someone or opens an incident is governed by your PagerDuty service's own settings — IMAA does not filter by severity, so send only the rules you want to page on to a PagerDuty channel.

Tier gating