Generic webhook
Send alerts from any tool to on-call with CallHeim.
Any tool — post our canonical alert JSON directly. 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.
Setting it up
Create a generic webhook integration in CallHeim to get an ingest URL, then POST a JSON object to it from your script, tool or pipeline. CallHeim reads title, severity, body and dedupKey, and a no-code field mapping picks out the fields you want from any other JSON. The snippet beside this is a working request, with {{WEBHOOK_URL}} replaced by your real URL.
If you generate a signing secret on this integration, CallHeim requires a valid HMAC-SHA256 signature of the raw request body in the X-CallHeim-Signature header on every request to it. Without a signing secret, the integration URL is the credential: keep it secret.
# Any system — POST canonical JSON:
curl -X POST "{{WEBHOOK_URL}}" \
-H 'content-type: application/json' \
-d '{"title":"...","severity":"P2","body":"...","dedupKey":"..."}'After it arrives
What CallHeim does with the alerts you send.
Anything that can POST a JSON object can raise an alert. A no-code mapping (dot and bracket paths — a JSONPath subset, not the full spec) picks out the fields you care about, and the alert joins the same pipeline as every cataloged source.
CallHeim reads the severity from the field you send or map, 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 →
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 →
Post a test alert and see what CallHeim does with it.
Start on the free trial, connect your first tool and send a test alert to see the incident it opens.