Skip to content

Push Notification

Deliver a notification to your phone — with the browser closed and no tab focused. This is the sink that completes the watcher story: an Element Change Trigger detects a change, Digest batches it, and this delivers it to a device.

Sends a push notification via ntfy or Pushover, with a title, priority, and a click-through URL so the notification can open the page it’s about. Pick the provider and its fields appear.

ProviderWhyAuth
ntfyOpen source, self-hostable, works with no account — just publish to a topic. The lowest-friction path.None for public topics; a Bearer token for a protected server.
PushoverA polished app with a one-off purchase, for reliability over self-hosting.An application token + your user key.
SettingNotes
TopicThe topic to publish to. Anyone who knows it can read it — pick something unguessable.
Message / TitleThe notification body and title.
PriorityMin, Low, Default, High, or Max.
TagsEmoji shortcodes (e.g. warning, tada) render as icons.
Click URLOpen this URL when the notification is tapped.
ServerDefaults to https://ntfy.sh; set your self-hosted URL for a private instance.
SettingNotes
Message / TitleThe notification body and title.
PriorityLowest, Low, Normal, or High.
Click URL / Click URL titleA URL to include, and its label.
  • ntfy (public topic): no credential needed — leave it empty. For an access-controlled server, use a Bearer Token credential.
  • Pushover: create an application at pushover.net for the application token, and copy your user key from your dashboard. Store both as a Basic Auth credential:
    • Username → the Pushover application token
    • Password → your Pushover user key
  • Tokens are stored in your credential vault and never pass through awflow’s backend.

This node is extension-only. Self-hosted ntfy servers are often on localhost or a LAN address — reachable through the extension’s host permissions, but not from the web build.

  • ntfy notification never arrives — subscribe to the exact same topic in the ntfy app, and confirm the Server matches (default https://ntfy.sh).
  • Pushover user key is invalid — check the credential: Username must be the application token, Password your user key (a common mix-up).
  • Click URL doesn’t open — provide an absolute https:// URL.