Incident & ITSM

Send PagerDuty alerts to on-call with CallHeim.

Incident events from a PagerDuty V3 webhook subscription. CallHeim maps the payload, attaches repeats to the incident that is already open, and pages whoever is on call for the service it belongs to.

pagerdutysource names also accepted: pager-duty, pd

Setting it up

Create an Integration in CallHeim and choose PagerDuty from the Catalog. You get an ingest URL for that integration, which you paste into PagerDuty’s webhook configuration. CallHeim’s ingest URL takes a JSON request body. The snippet beside this is the shape it expects, with {{WEBHOOK_URL}} replaced by your real URL.

PagerDuty signs its webhooks with its own header, which CallHeim does not verify. Do not set a signing secret for this integration, because every delivery would then be rejected. The integration URL is the credential: keep it secret, and if it is exposed, disable the integration and create a new one.

CallHeim includes a payload mapping for PagerDuty’s webhook format.

PagerDuty documentation →

Setup snippetpagerduty
# PagerDuty → Integrations → Generic Webhooks (v3) → New Webhook
# Webhook URL: {{WEBHOOK_URL}}
# Subscribe to incident.triggered / incident.resolved events.
Check PagerDuty’s current documentation for the exact fields.

After it arrives

What CallHeim does with PagerDuty alerts.

Incidents and tickets raised in another system can open an incident here for paging and escalation. A repeat carrying that system’s own identifier attaches to the incident already open for it, however long after the first. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages instead. CallHeim does not write status back to the source system.

CallHeim maps PagerDuty’s severity or priority field to a P1 to P5 level where the source sends one, and shows a separate, explainable severity suggestion that a person can apply. How severity is suggested →

Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged. Alerting and escalation →

If PagerDuty sends a recovery notification, CallHeim records it against the incident.

The thresholds it passes through

Repeat, sender-supplied dedup key
attaches, any age
Repeat, title or subject only
attaches, incident under 24 h old
Flap threshold
4 transitions / 600s
Title correlation
similarity ≥ 0.6, same source and service
Group window default
600s

All defaults are published. You can turn title correlation off or change its threshold, and set the window on your own noise rules; the dedup rule and the flap settings are fixed. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages. How alerts are processed →

CallHeim

Point PagerDuty at CallHeim and see what it does with your alerts.

Start on the free trial, connect PagerDuty and send a test alert to see the incident it opens.