Short answer: Drop the "ntfy → ntfy Send with Tags + Priority" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Topic topic | string | Required | — |
Message message | string | Required | — |
Title title | string | Optional | — |
Tags (comma-separated) tags | string | Optional | warning,fire |
Priority priority | options | Optional | — |
{"topic": "{{trigger.topic}}","message": "{{trigger.message}}","title": "{{trigger.title}}","tags": "warning,fire","priority": "{{trigger.priority}}"}
{"id": "msg_abc","time": 1620000000,"topic": "alerts","message": "Hi"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.