Per-pair page

Connect ntfy to Slack in two minutes.

Real-time triggers from ntfy, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Connect ntfy to Slack — start free See reverse direction

Trigger app

ntfy as the trigger

Workflows fire when something happens in ntfy.

ntfy has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

ntfy → Slack

When something happens in ntfy, do it in Slack.

0 ntfy triggers wired to 45 Slack actions.

Slack → ntfy

Or fire it the other way around.

13 Slack triggers wired to 2 ntfy actions downstream.

See Slack → ntfy →

How it works

Connect ntfy and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize ntfy and Slack
Open TinyCommand, authorize ntfy and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a ntfy trigger
Drop the ntfy → New event trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/ntfy.event
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Slack action
Drop the Slack → Add Reaction action below it. Map fields from the ntfy payload into the Slack inputs.
slack.add-reaction
5
Publish
Publish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about ntfy + Slack.

How long does it take to connect ntfy and Slack on TinyCommand?

Under two minutes. Authorize ntfy and Slack once each, drop the ntfy trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the ntfy ↔ Slack integration real-time?

Yes. Both ntfy and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between ntfy and Slack?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.

What ntfy events can trigger a Slack workflow?

Use TinyCommand's universal Webhook trigger to receive ntfy events, then run any of the 45 Slack actions downstream.

Do I need a paid plan to use ntfy with Slack?

No. There's a free tier that covers most ntfy+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Slack → ntfy instead?

Build it the same way, in reverse. There's a dedicated /integrations/slack/with/ntfy page with the reverse-direction triggers and actions.