Can ntfy and Slack talk in both directions?

Yes. Build one flow that starts in ntfy and acts in Slack, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect ntfy to Slack

Move data between ntfy and Slack the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore ntfy Explore Slack

ntfy triggers: 1
ntfy actions: 8
Slack triggers: 14
Slack actions: 29

Automation ideas

What you can build with ntfy and Slack

A few flows teams run between ntfy and Slack. Use one as a starting point, or build your own from scratch.

New Message in ntfy creates Add Reaction to Message in Slack
Triggers when a message is published to a ntfy topic. Needs the server to cache messages (ntfy.sh keeps them 12 hours); messages sent with "Do not cache" are never seen.
New Public Message Posted Anywhere in Slack creates Send Notification in ntfy
Triggers when a new message is posted to any channel.
New Message in ntfy creates Send Message To A User in Slack
Triggers when a message is published to a ntfy topic. Needs the server to cache messages (ntfy.sh keeps them 12 hours); messages sent with "Do not cache" are never seen.
New Public Message Posted Anywhere in Slack creates Send File in ntfy
Triggers when a new message is posted to any channel.
New Message in ntfy creates Send Message To Multiple Users in Slack
Triggers when a message is published to a ntfy topic. Needs the server to cache messages (ntfy.sh keeps them 12 hours); messages sent with "Do not cache" are never seen.
New Public Message Posted Anywhere in Slack creates Update Notification in ntfy
Triggers when a new message is posted to any channel.