Incident & ITSM

Send ServiceNow alerts to on-call with CallHeim.

Event Management events / ITSM incidents via 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.

servicenowsource names also accepted: service-now, snow, servicenow-em

Needs a forwarder

ServiceNow 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.

ServiceNow events or incidents you forward from your own instance become CallHeim alerts: repeats on the same event or incident collapse onto one incident, and the service the integration is bound to pages whoever is on call for it. You build the Business Rule in ServiceNow that sends them. CallHeim includes a payload mapping for ServiceNow’s webhook format. CallHeim does not write status back to ServiceNow.

How the alert reaches on-call

  1. Step 1An Event Management event lands in em_event, or an incident is created or updated.
  2. Step 2A Business Rule you write on that table calls an Outbound REST Message (RESTMessageV2) to POST a JSON body to your CallHeim ingest URL.
  3. Step 3CallHeim reads message_key (or the event's node and resource, or the incident number) as the identity signal, and maps the event's numeric severity or the incident's priority.
  4. Step 4A repeat with the same identity 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

    Create the ServiceNow integration in CallHeim to get an ingest URL.

  2. 02

    Build an Outbound REST Message in ServiceNow pointed at that URL.

    System Web Services > Outbound > REST Message. Define a POST method with a JSON body built from the fields you want CallHeim to read (see Field mapping).

  3. 03

    Write a Business Rule that calls it.

    On em_event insert (Event Management), or on incident insert/update, depending on which record type you want mirrored. Use RESTMessageV2 in the rule's script to send the request.

  4. 04

    Shape the body as either the flat event fields or the incident-wrapped shape.

    CallHeim's parser accepts either { source, node, type, resource, metric_name, severity, description, message_key, additional_info } for an Event Management event, or { incident: { number, short_description, priority, state } } for an ITSM incident — pick one and be consistent.

Example payloadJSON
{
  "source": "Prometheus",
  "node": "app-node-3",
  "type": "High CPU",
  "resource": "CPU",
  "severity": "1",
  "description": "CPU utilization above 95%",
  "message_key": "app-node-3:cpu",
  "additional_info": "sustained for 10m"
}
Example payload in the fields the parser reads for a ServiceNow Event Management event; check ServiceNow's own documentation for the em_event schema.

What CallHeim reads from the payload

Payload fields and what each one maps to on the incident
Payload fieldMaps toNote
incident.short_description / incident.number (ITSM shape)incident title
description / resource / metric_name (event shape)incident title
severity ("1" Critical … "5" OK/Clear), event shapeseverity1→P1, 2→P2, 3 or 4→P3, 5 or 0→P4.
incident.priority, ITSM shapeseverity1→P1, 2→P2, anything else→P3; a resolved or closed incident state writes P4.
additional_info, or type / node / source joined togetherincident body
message_key (event shape) or incident.number (ITSM shape)identity signalServiceNow's own dedup key for the event shape.

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 message_key on the event shape, or the incident number on the ITSM shape, so a Business Rule that resends the same record's key collapses repeats onto one CallHeim incident, at any age, because the key is the sender's own.

Recovery

On the incident shape, an incident state of resolved or closed (or 6 or 7) is recorded against the incident; send a test update from your own instance to see the result before you rely on it. On the event shape, a severity of 5 or 0 is recorded as P4. CallHeim does not write status back to ServiceNow.

Troubleshooting

Common problems and how to fix them
ProblemFix
Nothing arrives.Check the Business Rule actually fires on the condition you expect (insert vs. update), and that the Outbound REST Message's endpoint matches the CallHeim ingest URL exactly.
HTTP 400 on send.The Business Rule's script built a body that is not the flat event shape or the { incident: {...} } shape CallHeim reads — check the JSON matches one of the two exactly.
A resolved incident stays open in CallHeim.On the incident shape, check that the state is resolved, closed, 6 or 7 and that the rule resends the same incident number. On the event shape, resolve the incident in CallHeim.
Repeats open separate incidents.The earlier incident had already been resolved, or message_key (or the incident number) is not stable across the events you are forwarding — check the Business Rule builds it the same way every time.
HTTP 401 once you enabled signing.ServiceNow 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

A fixed header value in ServiceNow's Outbound REST Message 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.

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

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