INTEGRATION
PagerDuty
Open and resolve PagerDuty incidents from ZnowPulse with a stable dedup key.
Pro planVisit PagerDuty
How the wire-up works
Three things to know: the protocol, the credential, and what the alert payload looks like. The setup is the same on free and Pro.
- Protocol
- webhook
- Credential
- PagerDuty Events API v2 integration key (a 32-char UUID).
- Payload
- Events API v2 with a deterministic dedup_key per monitor+state. ZnowPulse sends trigger on DOWN, resolve on UP. Re-opening an incident after a flap sends acknowledge followed by a fresh trigger under the same dedup_key.
What it supports
The grid below describes what the channel itself supports once wired up. All channels are available on the free plan unless the badge says otherwise.
Free planNot supportedRequires Pro.
Pro planSupportedSame on free and Pro.
InteractiveSupportedTwo-way — buttons in the alert acknowledge the incident in ZnowPulse.
Incoming mentionsSupportedCan receive replies or status changes from the channel.
Rich attachmentsSupportedCards, embeds, colour-coded status.
TLS in transitSupportedHTTPS / WSS — no plaintext fallback.
When PagerDuty is the right pick
You have an on-call rotation and you want ZnowPulse's DOWN to open a real incident with the right people paged, not a chat notification that someone has to notice.
Wire PagerDuty to ZnowPulse in two minutes.
Free plan. No card. Cancel any time.