Skip to content
StatusOwlDocs

ntfy

Push alerts to ntfy.sh or a self-hosted ntfy server, with priority and tags.

Last updated

ntfy is a small HTTP pub-sub service for push notifications. StatusOwl publishes to a topic that your phone or desktop subscribes to. It is the closest thing to a push alert StatusOwl offers, and it costs nothing to run.

What it supports

  • The public https://ntfy.sh server or any self-hosted deployment.
  • Optional bearer-token authentication for protected topics.
  • Priority (1–5) and tags, set per integration.

Setting it up

  1. Install the ntfy app (iOS or Android) or subscribe in the web client.
  2. Pick a long, hard-to-guess topic name — statusowl-acme-oncall-9f2a, not alerts.
  3. In StatusOwl, go to Integrations → Add Integration and choose ntfy.
  4. Leave the server URL as https://ntfy.sh, or point it at your own server.
  5. Enter the topic, set a priority, add tags, and — for protected topics — an auth token.
  6. Click Save, then Send Test.
On ntfy.sh, the topic name is the only secret

Anyone who knows a topic name on the public server can read messages published to it. Use a long random name, or self-host with access-control lists and an auth token. Do not name a topic after your company.

Self-hosted ntfy

Point Server URL at your own server, e.g. https://ntfy.yourcompany.com. StatusOwl validates the hostname at save time and again at send time: private ranges, loopback addresses and cloud metadata endpoints are refused. A self-hosted server has to be reachable from the public internet for StatusOwl to publish to it.

Priority and tags

Priority runs 1 (minimum) to 5 (maximum) and applies to every message this integration sends. Tags are a comma-separated list, also applied to every message. Use them to force genuinely urgent rules to the top of the tray and to separate environments — one integration at priority 5 tagged prod, another at priority 2 tagged staging, each routed from different alert rules.

What arrives here today

  • Send Test messages from the dashboard.
  • Watch Owl alert rules routed to this integration, on fire and on resolve, published with the configured priority and tags.

Nothing else dispatches. A failing HTTP, ping or TCP check does not push to ntfy — see Notifications overview.

See also