INTEGRATION
ntfy
Push notifications to a self-hosted or public ntfy.sh topic. No account needed.
Free planVisit ntfy
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
- ntfy
- Credential
- Server URL (e.g. https://ntfy.sh) + topic (e.g. znowpulse-alerts) + optional username + password (basic auth).
- Payload
- JSON body with title (subject), message (alert text), priority, and content-type markup tags. Headers carry topic routing.
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 ntfy is the right pick
You want push-style alerts to your phone without giving any third party your phone number. Self-host ntfy on a cheap VPS and the entire path stays between you and ZnowPulse.
Wire ntfy to ZnowPulse in two minutes.
Free plan. No card. Cancel any time.