Skip to content

ntfy integration

Push alerts to ntfy.sh or a self-hosted ntfy server.

Last updated May 9, 2026

ntfy is a simple HTTP-based pub-sub service for push notifications. StatusOwl can publish alerts to a topic that's subscribed on your phone or desktop.

Overview

  • Works with the public https://ntfy.sh server 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

  1. Install the ntfy app on your phone (iOS / Android) or subscribe in the web client.
  2. Pick a unique, hard-to-guess topic name (e.g. statusowl-acme-oncall-9f2a).
  3. In StatusOwl, go to Integrations → Add Integration and choose ntfy.
  4. Leave the server URL as https://ntfy.sh (or point at your self-hosted server), and enter the topic.
  5. Set priority, optional tags, and — for private topics — an auth token. Choose which events to subscribe to (see event coverage for what currently fires).
  6. 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 alerts to the top of the notification tray and categorizing messages by environment.

What currently sends to this integration

Per the integrations overview, ntfy integrations receive:

  • Send Test events fired from the dashboard.
  • Watch Owl alert rules — when a host-metric rule routes to this integration, firing and resolving alerts publish to the topic with the integration's configured priority and tags.

Uptime-monitor state changes (down / recovery / maintenance) are configured on the integration but not yet dispatched. The flags are ready for the dispatch service when it ships.

See also