INTEGRATION

Opsgenie

Open and close Opsgenie alerts from ZnowPulse with a stable dedup key.

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
Opsgenie API key (from Settings → API integration) + region (US or EU).
Payload
Opsgenie Alert API; ZnowPulse sends create on DOWN and close on UP, with a deterministic alias per monitor so a flap does not multiply incidents.

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 Opsgenie is the right pick

You are already on Opsgenie for on-call and you want ZnowPulse to create real incidents instead of just pinging a chat window someone has to watch.

Wire Opsgenie to ZnowPulse in two minutes.

Free plan. No card. Cancel any time.