IncidentRelay Integrations | Alert Sources, Notifications and Calendars

Complete integration catalog

All integrations below are included in IncidentRelay 2.2. Every inbound source uses the same route and intake-token model, so adding a monitoring system does not require a separate incident workflow.

Available now

Incoming alert sources

These integrations create, update or resolve alerts and connect them to an IncidentRelay route.

Prometheus Alertmanager Available now Receive grouped webhook alerts, labels, annotations and recovery events. Azure Monitor Available now Receive common-alert-schema webhooks, normalize monitor conditions and resolve recovered alerts. AWS SNS and CloudWatch Available now Verify signed SNS messages and normalize CloudWatch alarm state changes. Grafana Alerting Available now Route Grafana alert instances with labels, source links and recovery handling. Datadog Available now Receive monitor triggers and recoveries through the native Datadog Webhooks integration available since v1.2.1. Uptime Kuma Available now Accept standard DOWN, UP, PENDING and MAINTENANCE webhook events with monitor-based deduplication. Zabbix Available now Normalize triggers, hosts, tags, severity, event links and recovery events. Sentry Available now Verify signed Sentry webhooks and route issue or metric alerts by project and environment. LibreNMS Available now Receive API Transport payloads and normalize device alert lifecycle events. RMON Available now Route monitoring checks by region, check type, target and lifecycle state. Generic webhook Available now Send custom JSON alerts and recoveries from internal tools or automation. PagerDuty Events API v2 Available now Use the compatible trigger, acknowledge and resolve event format with an IncidentRelay route key. Heartbeats Available now Monitor cron jobs, backups and distributed workers with dead-man-switch pings and overdue alerts.

Notifications and responder delivery

These integrations deliver routed incidents or profile-level notifications to the people who can respond.

Slack Available now Use incoming webhooks or Bot API delivery with ACK/Resolve actions, message updates and Socket Mode. Mattermost Available now Send channel notifications with optional interactive acknowledgement, resolve actions and updates. Telegram Available now Deliver bot notifications with optional inline actions and alert links. Email Available now Send alert notifications through SMTP to the assigned responder email. Discord Available now Deliver incident notifications to Discord through webhook-based channels. Microsoft Teams Available now Deliver incident notifications to Microsoft Teams through webhook-based channels. Outbound webhook Available now POST notification payloads to a custom HTTP endpoint for internal automation. Voice calls Available now Call the assigned responder through a configurable voice provider with optional keypad actions. Browser and PWA push Available now Send profile-level notifications and one-time ACK/Resolve actions to subscribed devices.

Calendar connections

Export IncidentRelay on-call schedules into the calendar tools responders already use.

CalDAV Available now Expose accessible team schedules as read-only calendars for Apple Calendar, Thunderbird and DAVx5. ICS calendar feeds Available now Subscribe to tokenized team calendars from Outlook, Google Calendar and other ICS clients.

How the pieces fit together

Alert source -> IncidentRelay route -> team and schedule
             -> notification or responder delivery -> ACK / Resolve

IncidentRelay schedule -> CalDAV or ICS -> external calendar

Incoming sources create or update alerts. Notification channels and profile-level delivery methods reach responders after routing. Calendar integrations export on-call schedules and do not receive alerts.

How to evaluate the fit

Start with one realistic flow: choose an incoming source, define route matchers, attach delivery channels, verify the current on-call assignment and test acknowledgement plus escalation. Use a non-production route first, then promote the tested configuration to production.