Overview
This node sends notifications using the ntfy.sh service, a simple and open-source notification server. It allows users to publish messages to specific topics, which can then be received by subscribers of those topics. This is useful for alerting, monitoring, or any scenario where you want to push real-time notifications from workflows.
Common use cases include:
- Sending alerts about system events or errors.
- Broadcasting updates or messages to a team.
- Triggering mobile or desktop notifications via ntfy.sh clients.
For example, you could configure this node to send a high-priority message to a topic whenever a critical error occurs in your workflow.
Properties
| Name | Meaning |
|---|---|
| Topic | The topic name to which the message will be published. Subscribers listen to this topic. |
| Message | The main content of the notification message. |
| Title | An optional title for the notification. |
| Priority | The priority level of the message. Options: Min (1), Low (2), Default (3), High (4), Urgent (5). |
| Click URL | A URL that will be opened when the notification is clicked. |
| Tags | Comma-separated tags associated with the message, used for filtering or categorization. |
| Additional Fields | Collection of optional fields: |
| - Alternate ntfy.sh Server URL | Use a custom ntfy.sh server URL instead of the default https://ntfy.sh. |
| - Authentication Token (Bearer) | Bearer token for authenticating requests to the ntfy.sh server if required. |
Output
The node outputs an array of JSON objects corresponding to the responses from the ntfy.sh server for each message sent. Each object contains the HTTP response data returned by the server after posting the notification.
No binary data output is produced by this node.
Dependencies
- Requires access to the ntfy.sh notification server, either the public one at https://ntfy.sh or a self-hosted instance.
- If the server requires authentication, a bearer token must be provided.
- No additional external libraries beyond standard HTTP request capabilities are needed.
- No special environment variables or n8n credentials are mandatory unless using authentication.
Troubleshooting
Common issues:
- Incorrect topic names or empty required fields will cause the request to fail.
- Network connectivity problems to the ntfy.sh server will prevent message delivery.
- Using an invalid or missing bearer token when the server requires authentication will result in authorization errors.
- Malformed tags (e.g., spaces not properly removed) might cause unexpected behavior.
Error messages:
- HTTP 401 Unauthorized: Check that the bearer token is correct and has proper permissions.
- HTTP 404 Not Found: Verify the ntfy.sh server URL and topic existence.
- Network errors/timeouts: Ensure the server URL is reachable and there are no firewall restrictions.
To resolve these, verify all input parameters, confirm server accessibility, and ensure authentication tokens are valid.