Overview
This node sends messages to the ntfy.sh notification service. It allows users to publish notifications with customizable topics, message content, titles, priorities, and other options. This is useful for alerting or informing users or systems about events, status updates, or important information in real-time.
Common scenarios include:
- Sending alerts from monitoring systems.
- Notifying teams about deployment statuses.
- Broadcasting reminders or scheduled messages.
- Integrating with workflows that require push notifications.
For example, you can send a high-priority message titled "Server Down" to a topic named "alerts" with a clickable URL directing to the incident dashboard.
Properties
| Name | Meaning |
|---|---|
| Topic | The topic name under which the message will be published on ntfy.sh. |
| Message | The main content of the notification message. |
| Title | An optional title for the notification. |
| Priority | The priority level of the message. Options: Min, Low, Default, High, Urgent. |
| Click URL | A URL that will be opened when the notification is clicked. |
| Tags | Comma-separated tags associated with the message (spaces are removed). |
| Delay | Schedule delivery for later using Unix timestamp, duration (e.g., 30m, 3h), or natural language (e.g., tomorrow 3pm). Minimum delay is 10 seconds, maximum is 3 days. |
| Additional Fields | Collection of extra options: |
| - 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 if the ntfy.sh server requires it. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each object contains the response from the ntfy.sh server after sending the notification.
If the server returns any data, it will be included in the json output field. The node does not handle binary data output.
Dependencies
- Requires access to the ntfy.sh notification service or a compatible server.
- If using a custom ntfy.sh server, its URL must be provided.
- If the server requires authentication, a bearer token must be supplied.
- No additional external libraries beyond standard HTTP request helpers are needed.
Troubleshooting
Common issues:
- Incorrect topic or message fields may cause the notification to fail or be ignored.
- Invalid or missing bearer token when required by the server will result in authentication errors.
- Providing an invalid custom server URL may cause connection failures.
- Delay values outside the allowed range (less than 10 seconds or more than 3 days) might be rejected.
Error messages:
- HTTP 401 Unauthorized: Check the bearer token and ensure it is valid.
- Network errors: Verify the server URL and network connectivity.
- Validation errors from ntfy.sh: Confirm all required fields are correctly set.