Can ntfy and Bluesky talk in both directions?

Yes. Build one flow that starts in ntfy and acts in Bluesky, 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 Bluesky

Move data between ntfy and Bluesky 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 Bluesky

ntfy triggers: 1
ntfy actions: 8
Bluesky triggers: 4
Bluesky actions: 5

Automation ideas

What you can build with ntfy and Bluesky

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

New Message in ntfy creates Create Post in Bluesky
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 Posts by Author in Bluesky creates Send Notification in ntfy
Triggers when a selected author creates a new post
New Message in ntfy creates Like Post in Bluesky
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 Posts by Author in Bluesky creates Send File in ntfy
Triggers when a selected author creates a new post
New Message in ntfy creates Repost Post in Bluesky
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 Posts by Author in Bluesky creates Update Notification in ntfy
Triggers when a selected author creates a new post