ntfy integration for Gladys Assistant

Send push notifications through ntfy (ntfy.sh or self-hosted).
Overview
This integration lets Gladys Assistant send push notifications through ntfy, a simple notification service. When a scene sends a message to you, it is pushed to your phone through the ntfy app.
It works with the free public server https://ntfy.sh as well as with your own self-hosted ntfy server.
This is a send-only channel: Gladys only sends notifications, it does not receive messages back. Each Gladys user configures their own ntfy topic in their account, so everyone gets their notifications on their own phone.
Prerequisites
- The ntfy app installed on your phone (Android / iOS), or any ntfy client.
- Internet access from your Gladys instance (to reach https://ntfy.sh), or a reachable self-hosted ntfy server.
- A topic and an access token for it. A topic is a channel; pick a
long, hard-to-guess name and protect it with a token (
tk_…) allowed to publish to it.
Configuration
The configuration has two parts:
1. Integration settings (shared, set once)
- ntfy server URL —
https://ntfy.shby default, or your self-hosted server; - Default priority — the priority of the notifications Gladys sends;
- Default notification title — the title shown on those notifications.
2. My account (per user)
Each Gladys user opens the integration and fills their own account block:
- Your ntfy topic — the topic your notifications are sent to;
- Access token — an ntfy access token (
tk_…) allowed to publish to that topic.
Then subscribe to that topic in the ntfy app on your phone so the notifications reach you.
Sending notifications
Use a Gladys scene with a "Send a message" action, choose this integration and the user to notify: the message is published to that user's ntfy topic and pushed to their phone.
Troubleshooting
- A user gets no notification — check that their topic and access token are filled in their account block, and that the ntfy app on their phone is subscribed to the same topic and server.
- Publishing fails (403) — the access token is missing or not allowed to publish to the topic; create/renew it on your ntfy server.
- Notifications arrive without a title — set the Default notification title in the integration settings.
Configuration settings
These are the settings ntfy asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| ntfy server URL | string | Yes | The base URL of the ntfy server, shared by everyone. Use the public https://ntfy.sh or your own self-hosted server. |
| Default priority | select | No | Priority applied to the notifications sent by Gladys. |
| Default notification title | string | No | Title shown on the notifications sent by Gladys. |
How to install ntfy in Gladys
- In Gladys, open Integrations: ntfy appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/callemand/gladys-ntfy:1.0.0), starts it in a sandbox isolated from the core, and generates the integration's interface (devices, discovery and configuration). - Open the Configuration screen of the integration, fill in the settings, and save.
- You can also install it directly from its repository URL: https://github.com/callemand/gladys-ntfy.
ntfy requires Gladys >=4.62.0. The catalog inside Gladys refreshes every hour, so a new version becomes available at most one hour after its release.
Not running Gladys yet? It is free and open source: follow the installation guide to get started.
About external integrations
ntfy is an external integration: a community integration packaged as a Docker container and published on GitHub, that Gladys installs in one click and runs in a sandbox isolated from its core. It is published and maintained by callemand, not by the Gladys core team.
- Browse all external integrations
- Discover the native integrations built into Gladys
- Build and publish your own external integration
- Source code on GitHub — source of this documentation