ceven

Ntfy

Sends instant push notifications to your devices based on workflow events and retrieves cached topic messages to trigger automated responses.

Try Ntfy in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Ntfy integration

    • Describe the outcome and Ceven picks the right Ntfy calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Ntfy data, across all 12 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Ntfy access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Ntfy, when, and on whose behalf.
    • The agent pauses and asks when Ntfy is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Ntfy.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Ntfy action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Ntfy, and when to use it.

Publish message
Use this when you need to send a notification to a specific topic. Topics are created automatically if they do not exist.
Publish JSON message
Use this to send notifications with all parameters in the request body, which is ideal for integrations that cannot use custom headers.
Publish via GET
Use this for simple webhook integrations where PUT or POST methods are unavailable.
Fetch cached messages
Pull previously sent messages from a topic cache. Supports filtering by time or message ID.
Get latest message
Pull only the most recent message from a topic cache without subscribing to the full stream.
Fetch scheduled messages
Pull a list of messages that are queued for delivery at a future date.
Poll topic
Retrieve cached messages and close the connection immediately after delivery.
Subscribe with filters
Retrieve specific messages from a topic based on priority, tags, or content.
Subscribe to multiple topics
Pull cached messages from several topics in one API call using a comma separated list.
Get account info
Pull account data, usage limits, and tier details for the authenticated user.
Check service health
Verify if the Ntfy service is operational and responding correctly.
Get server stats
Pull metrics regarding message volume and publishing rates on the server.
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 confi
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.
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.
Fetch Latest Message from Topic
Tool to fetch the most recent message from a topic's cache. Use when you need to retrieve the latest message without subscribing to the topic stream.
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.
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.
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.
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.
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.
Poll Messages from Topic
Tool to poll for messages from an ntfy topic without maintaining a long standing connection. Use when you need to retrieve cached messages and have the connection close immediately after delivery. The connection ends after reading all avail
Publish Message as JSON to NTFY
Tool to publish messages as JSON to ntfy. Use when you need to send notifications with all parameters in the request body, especially useful for integrations that cannot add custom headers.
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.
Publish Message to Topic (PUT)
Tool to publish a message to a topic using PUT method. Use when you need to send notifications to subscribers of a topic. Supports various options like priority, tags, attachments, and scheduled delivery.
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 me
Send Message via Webhook
Tool to send messages via webhook endpoint using simple GET request. Use when you need a simple webhook style integration or for clients with limited HTTP support.
Subscribe to NTFY Topic with Filters
Tool to subscribe to a ntfy topic with filters based on message fields (id, message, title, priority, tags). Use when you need to retrieve specific messages from a topic using filter criteria. Returns matching messages from the topic as a J
Subscribe to Topic (JSON Stream)
Tool to subscribe to a ntfy topic and receive messages as JSON stream. Use when you need to retrieve cached messages from a topic. The action polls the topic and returns immediately with cached messages.
Subscribe to Multiple NTFY Topics
Tool to subscribe to multiple ntfy topics simultaneously using comma separated topic list. Use when you need to receive messages from multiple topics in a single API call. Returns cached messages when used with poll=true parameter.

30 actions · scroll to see them all

Frequently asked questions

Ceven interacts with Ntfy using the standard HTTP API. For public topics, no authentication is required and the agent sends messages directly to the topic URL. For private topics, you provide your Ntfy user credentials which Ceven stores encrypted. The agent then uses these credentials to authenticate via basic auth or token based headers depending on your server configuration. This ensures that only authorized workflows can publish to or read from your sensitive notification channels. You can rotate these credentials at any time in your Ceven connection settings to maintain security across your notification pipelines.
Yes. Ceven uses the poll and fetch cached messages actions to monitor Ntfy topics. You can set up a workflow that checks a topic every few minutes for a specific keyword or tag. When the agent finds a matching message, it can trigger any other tool in your stack, such as opening a Jira ticket or restarting a server. This effectively turns Ntfy into a lightweight event bus where a simple push notification from your phone can act as a command for an automated backend process.
The Ntfy hosted service has specific rate limits and storage quotas for the free tier. For example, there are limits on how many messages can be published per second and how long messages are cached on the server before they are deleted. If your workflow exceeds these limits, the Ntfy server will return a 429 Too Many Requests error. Ceven handles this by implementing a retry logic with exponential backoff, but for high volume enterprise needs, you should upgrade your Ntfy tier or use a self hosted instance to avoid message drops.
Ceven can publish messages that include attachments by referencing the file metadata and upload endpoints provided by Ntfy. When a workflow generates a report or a log file, the agent can upload that file to the Ntfy server and then send a notification to the topic containing the link to that attachment. This allows you to receive a push notification on your phone that leads directly to a diagnostic file, making it much faster to debug production issues without needing to log into a VPN or a remote terminal.
Notifications sent via the publish actions are delivered in real time. The latency is typically limited only by the network round trip between Ceven and the Ntfy server. However, if you are using Ceven to monitor a topic via polling, the latency depends on your polling interval. To get the fastest response, we recommend using a shorter polling window for critical topics, though you must be mindful of the server rate limits mentioned previously to avoid being temporarily blocked by the Ntfy API.
Yes. When connecting Ntfy to Ceven, you can specify your own server URL instead of using the default ntfy.sh domain. The agent will then direct all API calls to your private instance. This is the recommended setup for organizations with strict data residency requirements or those who need to bypass the rate limits of the hosted service. Just ensure that your Ntfy instance is reachable over the internet or via a configured gateway so that Ceven can communicate with the API endpoints.
Ceven uses the subscribe with filters action to narrow down the data it pulls from a topic. You can specify filters for priority levels, such as only pulling messages marked as high or urgent, or filter by specific tags. This prevents the agent from processing every single notification and focuses the workflow on actionable events. For example, you can configure a workflow to ignore all info level logs but immediately trigger an alert when a message with the tag critical appears in the Ntfy stream.
Ceven does not store your Ntfy messages in a permanent database. The agent fetches messages from the Ntfy cache to process them within the context of a running workflow. Once the workflow execution is complete, the message content is cleared from the active memory of the agent. The source of truth remains the Ntfy server. If you need a permanent record of notifications, we recommend adding a step to your workflow that archives the message into a database or a spreadsheet before the execution ends.

Alternatives to Ntfy

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Pushover logoPushoverPagerDuty logoPagerDutyPushbullet logoPushbullet

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Ntfy and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free