ntfy

Node catalog Actions

On this page

Publish a notification to ntfy.sh or your own ntfy server.

Usage and specifics

Configure the recipient, channel or topic and message for the provider. Ntfy and Apprise allow optional credentials depending on the server. Other services need dedicated access. Permissions, SMS charges and delivery limits remain service-specific.

Technical type : ntfy. Runtime : nodulz.

Credentials and prerequisites

ntfy (integration / ntfy). ntfy access token

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`credentialId`	`string`	`""`	-
`title`	`string`	`""`	-
`message`	`string`	`""`	-
`baseUrl`	`string`	`"https://ntfy.sh"`	-
`topic`	`string`	`""`	-
`priority`	`number`	`3`	-; ≥ 1, ≤ 5
`tags`	`string`	`""`	-
`clickUrl`	`string`	`""`	-
`attachmentUrl`	`string`	`""`	-

Configuration help

title Title: Optional. Workflow expressions are supported.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialId": "",
  "title": "",
  "message": "",
  "baseUrl": "https://ntfy.sh",
  "topic": "",
  "priority": 3,
  "tags": "",
  "clickUrl": "",
  "attachmentUrl": ""
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.