Skip to main content

ntfy

The ntfy trigger sends push notifications to any ntfy.sh topic or self-hosted ntfy server with priority levels, tags, and action buttons.

⚙️ Configuration Variables​

WUD_TRIGGER_NTFY_{trigger_name}_TOPIC
Requiredstring

Target ntfy topic name

Allowed values:Valid ntfy topic name
WUD_TRIGGER_NTFY_{trigger_name}_AUTH_PASSWORD
Optionalstring

Password (for Basic authentication)

WUD_TRIGGER_NTFY_{trigger_name}_AUTH_TOKEN
Optionalstring

Access token (for Bearer authentication on protected topics)

Allowed values:Bearer token
WUD_TRIGGER_NTFY_{trigger_name}_AUTH_USER
Optionalstring

Username (for Basic authentication)

WUD_TRIGGER_NTFY_{trigger_name}_PRIORITY
Optionalintegerdefault: 3

ntfy notification priority

Allowed values:Integer between `1` (min) and `5` (max) [see docs](https://docs.ntfy.sh/publish/#message-priority)
WUD_TRIGGER_NTFY_{trigger_name}_URL
Optionalurldefault: https://ntfy.sh

ntfy server base URL

Allowed values:Valid HTTP/HTTPS URL
info

This trigger also supports all common trigger configuration options (such as thresholds, scheduling, and batching).

🚀 Examples​

Public ntfy.sh Service​

services:
  whatsupdocker:
    image: getwud/wud
    environment:
      - WUD_TRIGGER_NTFY_LOCAL_TOPIC=my_unique_wud_topic
      - WUD_TRIGGER_NTFY_LOCAL_PRIORITY=3

Self-Hosted Protected ntfy Server​

services:
  whatsupdocker:
    image: getwud/wud
    environment:
      - WUD_TRIGGER_NTFY_LOCAL_URL=https://ntfy.example.com
      - WUD_TRIGGER_NTFY_LOCAL_TOPIC=alerts
      - WUD_TRIGGER_NTFY_LOCAL_AUTH_TOKEN=tk_1234567890abcdef