Integrations

Alert source integrations for on-call: 136 catalogued sources, one pipeline.

Each catalogued source has its own payload mapping and setup page, built and tested against sample payloads for that source’s webhook format.

136 sources

How ingest works

Create an Integration and CallHeim shows you its ingest URL. CallHeim verifies an HMAC-SHA256 signature on each source’s requests once you enable signing on that integration (the sending tool must be able to sign). Without a signing secret, the URL itself is the credential — a URL cannot be rotated, so disable the integration to revoke a source. The endpoint enqueues and returns; the processor drains the queue.

The ingest contract →

If your tool is not listed

The generic webhook accepts any JSON object, and a no-code mapping (dot and bracket paths) picks out the fields that matter. PagerDuty Events API v2 and legacy v1 bodies are also accepted as-is, so a tool that lets you set its Events API endpoint can often be repointed rather than rebuilt.

The generic webhook →

If it only sends email

Trial, Business and Enterprise plans: each workspace gets an inbound alert e-mail address for email-to-alert; mail sent to it becomes an alert. Starter and Pro do not include it. Available in early access.

On-call for IT operations →

CallHeim

Put a rule you can read between your alerts and your on-call.

CallHeim helps teams stay in control when critical systems are not. Explore the platform, connect one source, and send yourself a page.

Early access · every workspace starts with a 14-day trial for up to 5 seats, no card required