INTEGRATION
Gotify
Push notifications to a self-hosted Gotify server. Open-source, single binary, no cloud.
Free planVisit Gotify
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
- gotify
- Credential
- Server URL (e.g. https://gotify.example.com) + app token (a per-application token from the Gotify web UI).
- Payload
- JSON with title, message, priority, and extras.client::display.contentType for the client to render as markdown.
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 Gotify is the right pick
You already run Gotify at home or on a small VPS and want one more source feeding it. The token model is per-application, so you can revoke one channel without affecting the others.
Wire Gotify to ZnowPulse in two minutes.
Free plan. No card. Cancel any time.