Overview
What PagerDuty is
PagerDuty is an incident management platform that routes alerts to on-call responders through schedules, escalation policies, and services.
Courier delivers to PagerDuty using its Events API v2, so a notification can trigger an incident in PagerDuty as one channel in your stack, alongside every other channel you send through Courier.
You need a Courier account and an Events API v2 integration on a PagerDuty service, which gives you an Integration Key.
Why Courier
What you get with PagerDuty + Courier
Trigger incidents from a send
A Courier notification triggers a PagerDuty incident through the Events API v2, so on-call gets paged the same way you send every other message.
One channel among many
Add PagerDuty to a send that already reaches email, SMS, push, and inbox. No separate integration to build in your code.
Route by rules and preferences
Decide when a notification should page on-call versus reach a user directly, using Courier routing and preferences.
Set severity and source
Control the event action, severity level, and source sent to PagerDuty, and override the routing key per recipient when you need to.
Escalate inside a flow
Use Courier journeys to notify a user first, then page PagerDuty if there is no response, with delays and branching.
Reach responders where they are
Let PagerDuty handle schedules and escalation policies while Courier decides what triggers an incident and when.
Use cases
What teams build with it
Setup
Connect it in minutes
An admin adds PagerDuty once on the Integrations page in Courier. Once connected, PagerDuty behaves like any other channel in your sends.
FAQ
Frequently asked questions
Can I use PagerDuty with Courier?
Yes. Courier can send notifications to PagerDuty as an incident channel, so an alert routed through Courier opens a PagerDuty incident for your on-call team. It sits alongside email, SMS, push, and Courier Inbox in one Send API call.
Do I still need my own PagerDuty account?
Yes. Courier does not run incident management; it routes notifications into your existing PagerDuty account. You keep your own PagerDuty services, escalation policies, and on-call schedules, and Courier delivers alerts into them.
What do I need to connect PagerDuty to Courier?
You need an Events API v2 integration on a PagerDuty service, then its Integration Key. Add that key as the Routing Key on Courier's PagerDuty configuration page, along with a Source value, and Courier can start triggering incidents.
What triggers a PagerDuty incident from Courier?
A notification routed to the PagerDuty channel fires a trigger event action through the Events API v2, which opens an incident on the connected service. Any Courier notification you route to that channel becomes a PagerDuty incident.
Can I send incidents to different PagerDuty services per user?
Yes. Set profile.pagerduty.routing_key on a recipient's Courier profile and it takes precedence over the main configuration's routing key, so that user's incidents open on a different PagerDuty service. Without it, Courier uses the default Routing Key.
Can I override severity or source per message?
Yes. PagerDuty provider overrides in the message payload set the incident's severity and source per notification. Severity accepts info, warning, error, or critical; source identifies the affected host, overriding the Source configured at setup.
Does Courier replace PagerDuty?
No. PagerDuty still owns incident management and alerting; Courier simply routes notifications into it as one channel. The same event can also reach recipients by email, SMS, push, or Courier Inbox from the same send.
More
