AlphornBeta
Push NotificationsIntegration

Ntfy

Push notifications to phones via ntfy

Send push notifications to Android and iOS devices using ntfy, a simple, self-hostable push notification service. No app account required.

How it works

1

Configure

Add the channel in your Alphorn dashboard with your credentials.

2

Send a webhook

POST a JSON payload to your Alphorn webhook endpoint.

3

Delivered

Alphorn filters, routes, and delivers the notification automatically.

Use cases

  • Mobile alerts for server downtime
  • Personal task and reminder notifications
  • IoT event alerts on your phone

Configuration

  • ntfy server URL (public or self-hosted)
  • Topic name
  • Optional: authentication token

Send your first notification

One HTTP request is all it takes. Alphorn handles routing to Ntfy automatically.

Terminal
$ curl -X POST https://app.alphorn.dev/n/V1StGXR8_Z5jdHi6B-myT \
  -H "Authorization: Bearer $ALPHORN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title":"Deploy complete","message":"v2.1.0 is live","priority":3,"tags":["deploy"]}'

What Alphorn adds on top of Ntfy

Wiring Ntfy into your application directly is the easy part. What usually grows into a maintenance problem is everything around it: retries when the provider is having a bad day, backoff so you don't get rate-limited, fan-out to additional destinations when a rule fires, and a delivery log for debugging. Alphorn owns all of that on your behalf, so the integration code you write stays at one HTTP call forever.

Every notification is stored in a durable PostgreSQL-backed queue before Alphorn delivers it to Ntfy. If delivery fails, Alphorn makes up to five attempts with exponential backoff and records the failure in the delivery log. You can trigger a secondary notification when deliveries to a primary channel fail, for example, page an on-call engineer when a daily summary to a chat room stops going through. Filtering rules based on priority, tags, or JSON path expressions decide at runtime whether a particular payload reaches Ntfy or gets routed somewhere else entirely.

The same rules apply whether you're on the managed edition or running Alphorn yourself. The self-hosted edition is AGPL-3.0-or-later and ships as a single container, so you can deploy the exact same delivery pipeline on your own infrastructure, useful for regulated environments where notification data has to stay inside your own network.

Related push notifications integrations

Alphorn can route the same notification to multiple channels. Pair Ntfy with another push notifications destination:

Start routing to Ntfy

Free plan includes 3,000 messages/month. No credit card required.