Integrations

Alert source integrations for on-call: 135 cataloged sources, one pipeline.

Each cataloged source has its own payload mapping and setup page for that source’s webhook format.

135 sources

Not on the list? Any tool that can send a webhook works with the generic webhook and a field mapping, and on the Trial, Business and Enterprise plans you can forward alert e-mail to an inbound alert address.

How ingest works

Create an Integration and CallHeim shows you its ingest URL. Signed requests (HMAC-SHA256) are available for the generic webhook, GitHub Actions and GitHub Dependabot. For other sources the integration URL is the credential; a URL cannot be rotated, so disable the integration to revoke a source, and a signing proxy in front of the sender can add a signature. Inbound alerts are queued durably, with a dead-letter queue and alarms, so a burst of alerts is buffered while it is processed.

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 organization 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. On plans with email-to-alert, e-mail rules filter incoming mail and decide what opens or resolves an incident from the subject, sender or body.

On-call for IT operations →

CallHeim

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

Start a 14-day trial, connect one alert source and send yourself a test page.