Can ntfy and Resend talk in both directions?

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

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

ntfy triggers: 1
ntfy actions: 8
Resend triggers: 1
Resend actions: 22

Automation ideas

What you can build with ntfy and Resend

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

New Message in ntfy creates Send Email in Resend
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 Event in Resend creates Send Notification in ntfy
Triggers when a selected email, domain or contact event happens.
New Message in ntfy creates Send Batch Emails in Resend
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 Event in Resend creates Send File in ntfy
Triggers when a selected email, domain or contact event happens.
New Message in ntfy creates Get Email Status in Resend
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 Event in Resend creates Update Notification in ntfy
Triggers when a selected email, domain or contact event happens.