Incident & ITSM

Send Zenduty alerts to on-call with CallHeim.

Incident response — outbound alert webhooks. 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.

zendutysource names also accepted: zen-duty

Setting it up

Create an Integration in CallHeim and choose Zenduty from the Catalog. You get an ingest URL for that integration, which you paste into Zenduty’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.

Zenduty cannot sign its requests in a format CallHeim verifies, so the integration URL is the credential. Keep it secret, and if it is exposed, disable the integration and create a new one. Do not set a signing secret unless a signing proxy you run signs each request. With a secret set, every unsigned delivery is rejected.

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

Zenduty documentation →

Setup snippetzenduty
# Zenduty → Integrations → Outbound Webhook
# URL: {{WEBHOOK_URL}}
# Body includes {alert:{message, alert_type ("critical"|"resolved"|...), entity_id}}.
Check Zenduty’s current documentation for the exact fields.

After it arrives

What CallHeim does with Zenduty 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 Zenduty’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 Zenduty 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 Zenduty at CallHeim and see what it does with your alerts.

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