Incident & ITSM

Send Opsgenie alerts to on-call with CallHeim.

Alerts from an Opsgenie outgoing webhook integration. 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.

opsgeniesource names also accepted: ops-genie, atlassian-opsgenie

Vendor status

Atlassian is retiring Opsgenie: end of sale 4 June 2025, shut down 5 April 2027.

Opsgenie's outgoing webhooks become CallHeim alerts: repeats on the same alert collapse onto one incident, and the service the integration is bound to pages whoever is on call for it. CallHeim includes a payload mapping for Opsgenie’s webhook format.

How the alert reaches on-call

  1. Step 1An Opsgenie alert is created, acknowledged or closed.
  2. Step 2Opsgenie's outgoing webhook integration POSTs the action and the alert to your CallHeim ingest URL.
  3. Step 3CallHeim reads the alert's alias as the identity signal and maps its priority to a severity.
  4. Step 4A repeat on the same alias attaches to the incident that is already open for it.
  5. Step 5The integration's bound service selects an escalation policy, which pages the on-call tier.

Setting it up

  1. 01

    Add a Webhook integration in Opsgenie.

    Settings > Integrations > Add integration > Webhook, name it, and optionally assign it to a team.

  2. 02

    Enter your CallHeim ingest URL and turn the integration on.

    Create the Opsgenie integration in CallHeim first to get the exact ingest URL.

  3. 03

    Enable the Create, Acknowledge and Close actions.

    CallHeim reads all three.

Example payloadJSON
{
  "action": "Create",
  "alert": {
    "alertId": "a1b2c3",
    "tinyId": "42",
    "alias": "high-cpu-prod",
    "message": "High CPU on prod cluster",
    "description": "CPU > 90% for 10 minutes",
    "priority": "P1",
    "source": "Datadog"
  }
}
Example payload from an Opsgenie outgoing webhook; check Opsgenie's own documentation for the current fields.

What CallHeim reads from the payload

Payload fields and what each one maps to on the incident
Payload fieldMaps toNote
alert.message / top-level messageincident title
alert.priority (P1–P5)severityMaps directly, with P5 clamped to P4 — except a Close action, which always writes P4 regardless of priority.
alert.description / alert.source / integrationNameincident body
alert.alias (or alertId, or tinyId)identity signalOpsgenie's own dedup identity, so a follow-up acknowledge or close on the same alias attaches to the existing incident.

How CallHeim processes it

Routing

Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged.

Deduplication

A repeat of the same alert attaches to the incident that is still open for it in the same service, triggered or acknowledged, with no new incident and no new page. When the sender supplies its own dedup key (a PagerDuty dedup_key, an Opsgenie alias, a Datadog alert id, an Alertmanager fingerprint, or a dedupKey that is more than the alert title), this holds however late the repeat arrives. When the identity comes from the e-mail subject or the alert title, the repeat attaches only if the incident was triggered in the last 24 hours; after that it opens a new incident and pages. A repeat at P1 or P2 is not folded into an open P3, P4 or P5 incident: it opens a new incident and pages. Once an incident is resolved or closed, the next repeat opens a new incident. Identity is Opsgenie's own alias (its own dedup key), so a create followed by an acknowledge or a close on the same alias collapses onto one incident, and a repeat attaches at any age.

Recovery

When Opsgenie sends a Close action, CallHeim records it against the incident with severity P4. Send a test Close from your own Opsgenie integration to see the result in your organization before you rely on it.

Troubleshooting

Common problems and how to fix them
ProblemFix
A closed Opsgenie alert leaves the CallHeim incident open.Check that the Close action is enabled on the Opsgenie webhook integration and that the Close webhook carries the same alias as the Create. If it still stays open, resolve it in CallHeim.
No alerts arrive.The integration is created but not turned on — Opsgenie webhook integrations need an explicit "Turn on integration" step after saving.
Acknowledges do not attach to the original alert.Confirm alias is populated and identical between the create and the acknowledge — a source that generates a new alias per event breaks the link.
HTTP 400 on send.Check the Description and Details checkboxes are enabled in the integration if you rely on alert.description reaching CallHeim — by default those fields may be omitted or truncated.
HTTP 401 once you enabled signing.Opsgenie cannot send a signature computed for each request. Remove the signing secret from this integration, or put a proxy you run in front that signs each request.

Security

Opsgenie's outgoing webhook can send only fixed custom headers, which cannot carry a signature computed for each request. The integration URL is the credential: keep it secret, and if it is exposed, disable the integration and create a new one. A signing proxy you run in front of the sender can add an X-CallHeim-Signature header; without one, do not set a signing secret, because every unsigned delivery would be rejected.

Migration notes

Run in parallel during a move: CallHeim receives PagerDuty Events API v1 and v2 requests and Opsgenie outgoing webhooks, and alerts forwarded from Splunk On-Call, Squadcast (now SolarWinds Incident Response), Zenduty (now Xurrent IMR) and Grafana OnCall. Every sender needs its own CallHeim integration URL; existing PagerDuty routing keys are not reused.

Vendor documentation checked

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

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