Skip to main content
Technical Preview

Overview

A client-mode connector for a curated publish/subscribe slice of ntfy: Default BASE_ADDRESS is https://ntfy.sh (replace with your self-hosted origin). Topics use messaging/ntfy/<object>/<verb>.
Public ntfy.sh topics allow anonymous publish/subscribe. Self-hosted servers may enforce ACLs with Bearer tokens or Basic auth — pass Authorization via {value.json.token} / {value.json.basic_b64} placeholders and Hub secrets. Prefer hard-to-guess topic names; treat the topic as a shared secret on public hosts.

Basic Syntax

Events

Auth

  1. For public ntfy.sh topics: no credentials. Pick a hard-to-guess topic ([-_A-Za-z0-9], ≤64 chars).
  2. Set connector BASE_ADDRESS to https://ntfy.sh or your self-hosted URL.
  3. For self-hosted ACLs, pass token (Bearer) or basic_b64 on the MQTT payload; store secrets with Hub / GET SECRET "NTFY_TOKEN".
  4. Successful publish returns HTTP 200 with a JSON message object. Health returns HTTP 200 and {"healthy":true}.

Example payloads

PublishMessage (path/header placeholders on MQTT JSON; HTTP body is plain text via {payload}):
HTTP body example: Coreflux alarm: vibration above threshold — Zone A PublishJson (full JSON body including actions that HTTP-callback a Coreflux REST server):
GetLatest:
Health: empty payload / no placeholders required.
Last modified on October 21, 2026