Skip to main content
The PagerDuty Events API v2 inbound connector accepts the familiar trigger, acknowledge, and resolve event shape. Use it when a system already emits PagerDuty-compatible events and you want Squasher to own the incident workflow.
This is an inbound source. The PagerDuty notification destination sends Squasher incidents out to a PagerDuty service and uses a PagerDuty-issued integration key instead.

​
Create the connector

Create a PagerDuty Events API v2 source under Settings → Integrations. Use the returned Squasher secret as the event’s routing_key and send requests to the returned endpoint.

​
Send an event

Acknowledge or resolve the same incident by reusing dedup_key:

​
Incident behavior

  • dedup_key is the stable alert key. Keep it unchanged for trigger, acknowledge, and resolve.
  • trigger opens or updates an incident, acknowledge records a lifecycle update, and resolve resolves it.
  • payload.severity accepts PagerDuty’s critical, error, warning, and info values and maps them to Squasher’s sev-1 through sev-3 levels.
  • Component, group, class, and source fields are normalized for connector diagnostics; raw payloads and credentials are never stored in delivery history.
The routing_key is a Squasher-generated write-only secret. Rotating the connector keeps the previous key valid for 24 hours, so update every sender during the overlap and send a trigger and resolve test pair. Related: Inbound alert connectors, Alert Connectors API, PagerDuty destination.