Can ntfy and Mailgun talk in both directions?

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

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

ntfy triggers: 0
ntfy actions: 2
Mailgun triggers: 8
Mailgun actions: 9

Automation ideas

What you can build with ntfy and Mailgun

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

New Bounce Event in Mailgun creates Send Notification in ntfy
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Bounce Event in Mailgun creates Custom API Call in ntfy
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Complaint Event in Mailgun creates Send Notification in ntfy
Triggers when a recipient reports an email as spam in Mailgun
New Complaint Event in Mailgun creates Custom API Call in ntfy
Triggers when a recipient reports an email as spam in Mailgun