INTEGRATION
Generic Webhook
POST a JSON payload to any HTTPS endpoint. Wire ZnowPulse into anything that has a webhook receiver.
Free planVisit Generic Webhook
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
- Target URL (https only) + optional custom headers (e.g. Authorization: Bearer …) + HTTP method (default POST).
- Payload
- JSON with type (ENDPOINT_DOWN / ENDPOINT_RECOVERY), endpointName, endpointUrl, endpointType, status, timestamp, tags, groupName, errorMessage, statusCode, consecutiveFailures, latencyMs.
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 planSupportedNo card, no expiry.
Pro planSupportedSame on free and Pro.
InteractiveNot supportedOne-way push only.
Incoming mentionsNot supportedOutbound-only.
Rich attachmentsNot supportedPlain text or simple message.
TLS in transitSupportedHTTPS / WSS — no plaintext fallback.
When Generic Webhook is the right pick
You have an internal system that already has a webhook receiver — a Slack-compatible chat, a status page you control, an incident pipeline, a custom runbook — and you want to wire ZnowPulse into it without us supporting it natively.
Wire Generic Webhook to ZnowPulse in two minutes.
Free plan. No card. Cancel any time.