Overview
This node allows you to push messages to a specified topic on the ntfy.sh service, which is a simple and open-source notification service. It is useful for sending real-time notifications or alerts to topics that subscribers can listen to. Typical use cases include alerting systems, monitoring notifications, or any scenario where you want to broadcast messages to multiple recipients via ntfy.sh.
For example, you could use this node to send a "Hello world!" message to a topic named "mytopic", which would then be delivered to all subscribers of that topic.
Properties
| Name | Meaning |
|---|---|
| Topic | The topic name to which the message will be pushed. Example: mytopic. |
| Message | The content of the message to publish to the topic. Example: Hello world!. |
| Send Additional Headers | Whether to include extra HTTP headers with the request, allowing customization of message metadata. |
| Specify Headers Using... | Method to specify additional headers: either as individual fields ("Fields") or as a JSON object ("JSON"). |
| Header Fields | When using "Fields" option, add one or more custom header name-value pairs (e.g., X-Title: This is a title). |
| JSON Headers | When using "JSON" option, provide a JSON object representing custom headers (e.g., { "X-Title": "This is a title" }). |
Output
The node outputs the response from the ntfy.sh API in the json output field. This typically contains information about the success or failure of the message push operation. The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the ntfy.sh service.
- The base URL for the ntfy.sh API must be configured in the node credentials.
- No other external dependencies are required.
Troubleshooting
Common issues:
- Incorrect or missing topic name will cause the message not to be delivered.
- Invalid or missing API authentication token will result in authorization errors.
- Malformed additional headers (if used) may cause the request to fail.
Error messages:
- Authorization errors usually indicate invalid or missing API credentials; verify your API key and base URL.
- HTTP 404 or similar errors may mean the topic does not exist or the URL is incorrect.
- JSON parsing errors when specifying headers as JSON indicate malformed JSON input; ensure valid JSON syntax.