Uptime & synthetics
Send StatusCake alerts to on-call with CallHeim.
Uptime test state-change webhook. 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.
Needs a forwarder
StatusCake does not post to CallHeim on its own for this. You set up a forwarder, rule or script that sends the event to your CallHeim URL; the setup steps show what to send.
Setting it up
StatusCake’s Webhook URL posts URL-encoded form fields, and CallHeim’s ingest URL takes a JSON body. Add a small relay that reads the form fields and POSTs them as JSON to your CallHeim integration URL.
Create an Integration in CallHeim and choose StatusCake from the Catalog to get its ingest URL, and use that URL as the target of your forwarder. CallHeim’s ingest URL takes a JSON request body. The snippet beside this shows the request it expects, with {{WEBHOOK_URL}} replaced by your real URL.
StatusCake 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 StatusCake’s webhook format.
# StatusCake → Notification Groups (formerly Contact Groups) → Webhook URL
# URL: <your relay URL> Webhook Method: POST
# StatusCake sends the form fields Name, Status (Up or Down), StatusCode, URL and Tags.
# The relay POSTs them as JSON, for example {"Name": "...", "Status": "Down", "StatusCode": 500, "URL": "..."}, to {{WEBHOOK_URL}}.
# Attach the notification group to your uptime tests.After it arrives
What CallHeim does with StatusCake alerts.
Repeated failures from the same probe attach to the incident already open for that check: at any age when the tool sends its own check id, and within 24 hours of the incident opening when only the check name identifies it. Failures with different titles from the same source can still be grouped onto an open, unacknowledged incident within ten minutes, when the sender does not supply its own dedup key.
CallHeim maps StatusCake’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 StatusCake 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 →
Point StatusCake at CallHeim and see what it does with your alerts.
Start on the free trial, connect StatusCake and send a test alert to see the incident it opens.