Can Mailgun and Plunk talk in both directions?

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

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

Mailgun triggers: 8
Mailgun actions: 9
Plunk triggers: 0
Plunk actions: 5

Automation ideas

What you can build with Mailgun and Plunk

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

New Bounce Event in Mailgun creates Send Transactional Email in Plunk
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Bounce Event in Mailgun creates Track Event in Plunk
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Bounce Event in Mailgun creates Get All Contacts in Plunk
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Complaint Event in Mailgun creates Send Transactional Email in Plunk
Triggers when a recipient reports an email as spam in Mailgun