ntfy integration
Push alerts to ntfy.sh or a self-hosted ntfy server.
ntfy is a simple HTTP-based pub-sub service for push notifications. StatusOwl can publish monitor alerts to a topic that's subscribed on your phone or desktop.
Overview
- Works with the public
https://ntfy.shserver or any self-hosted deployment. - Supports optional bearer token authentication for private topics.
- Priority (1–5) and tags are configurable per integration.
Setting up ntfy
- Install the ntfy app on your phone (iOS/Android) or subscribe in the web client.
- Pick a unique, hard-to-guess topic name (e.g.
statusowl-acme-oncall-9f2a). - In StatusOwl, go to Integrations → Add Integration and choose ntfy.
- Leave the server URL as
https://ntfy.sh(or point at your self-hosted server), and enter the topic. - Set priority, optional tags, and — for private topics — an auth token. Select which events to fire on.
- Click Save, then Send Test.
Topic names are the security boundary
On the public ntfy.sh server, anyone who knows the topic name can read messages on it. Use a long, random topic name — or protect the topic with an auth token on a self-hosted server with access-control lists enabled.
Self-hosted ntfy
Point Server URL at your ntfy server (e.g. https://ntfy.yourcompany.com). StatusOwl validates that the hostname isn't a private or loopback address before saving, and again at send time — you can't point at localhost, RFC1918 ranges, or cloud metadata endpoints.
Priority and tags
Set a default priority (1 = minimum, 5 = maximum) and a comma-separated list of tags per integration. These are applied to every message this integration delivers — useful for forcing critical down alerts to the top of the notification tray and categorizing messages by environment.