# Ntfy AI integration on Definable

> Send push notifications to your phone or desktop via PUT/POST

## What this connects

Send push notifications to your phone or desktop via PUT/POST

Vendor: https://ntfy.sh/

## Tools available

**12** tools available. First 12:

- `NTFY_CREATE_ACCOUNT` — Create NTFY Account — Tool to register a new user account on ntfy. Use when you need to create a new user account on the ntfy.sh hosted service. Note: This endpoint is not available on self-hosted instances unless signup is explicitly enabled in the server configuration.
- `NTFY_CREATE_WEBPUSH_SUBSCRIPTION` — Create Web Push Subscription — Tool to register a web push subscription for browser notifications. Use when you need to enable push notifications from ntfy topics through a browser's native push notification system.
- `NTFY_DELETE_WEBPUSH_SUBSCRIPTION` — Delete Web Push Subscription — Tool to unregister a web push subscription from the ntfy server. Use when you need to remove browser push notifications for a previously registered endpoint.
- `NTFY_FETCH_SCHEDULED_MESSAGES` — Fetch Scheduled Messages — Tool to fetch messages scheduled for later delivery from a topic. Use when you need to retrieve messages that are set to be delivered at a future date. The poll=1 and scheduled=1 parameters are automatically set to retrieve cached scheduled messages in a single request.
- `NTFY_GET_ACCOUNT` — Get Account Information — Tool to retrieve account data for authenticated user or anonymous user. Use when you need to get account information, limits, statistics, or tier details.
- `NTFY_GET_STATS` — Get Server Statistics — Tool to retrieve server statistics including message counts and publishing rates. Use when you need to monitor ntfy server activity and get metrics about message volume.
- `NTFY_GET_TIERS` — Get Service Tiers — Tool to list all available ntfy service tiers with their limits and features. Use when you need to retrieve subscription tier information including pricing and usage limits. Requires that payments are enabled on the server.
- `NTFY_HEAD_FILE` — Get File Attachment Metadata — Tool to get file attachment metadata from a message without downloading the file content. Use when you need to check file size, content type, or verify file existence in the ntfy attachment cache.
- `NTFY_HEALTH_CHECK` — Check NTFY Service Health — Tool to check the health status of the ntfy service. Use when you need to verify if the ntfy service is operational and responding correctly.
- `NTFY_PUBLISH_MESSAGE` — Publish Message to Topic — Tool to publish a message to a ntfy topic. Use when you need to send notifications or alerts to a topic. Topics are created dynamically if they don't exist.
- `NTFY_PUBLISH_VIA_GET` — Publish Message via GET — Tool to publish messages to ntfy via GET request with URL parameters. Use when PUT/POST methods are unavailable or for simple webhook integration. Supports all message parameters as query strings. Without parameters, sends 'triggered' as message.
- `NTFY_SUBSCRIBE_RAW_STREAM` — Subscribe to Topic (Raw Stream) — Tool to subscribe to a topic and receive message bodies as raw text stream. Use when you need to retrieve messages without metadata like priority, tags, or titles. Each line in the response contains only the message body. Empty lines represent keepalive messages. In streaming mode, the connection remains open to receive new messages. With poll=1, cached messages are returned and the connection closes.

## Auth

Auth schemes: `API_KEY`, `BASIC`.

## How agents use Ntfy

Inside a Definable workflow, Ntfy is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Ntfy** — the Researcher (GPT-5.5) pulls context from Ntfy (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Ntfy** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Ntfy (create record, post message, draft email).
- **Designer / Engineer → Distributor → Ntfy** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Ntfy (attach file, open PR comment, post status).

The Verifier checks every Ntfy call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- notifications — https://definable.ai/apps/category/notifications/
- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/ntfy/
- Same category (notifications): https://definable.ai/apps/category/notifications/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt