Can ntfy and Heartbeat talk in both directions?

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

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

ntfy triggers: 1
ntfy actions: 8
Heartbeat triggers: 0
Heartbeat actions: 2

Automation ideas

What you can build with ntfy and Heartbeat

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

New Message in ntfy creates Create User in Heartbeat
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 Message in ntfy creates Custom API Call in Heartbeat
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.