Can Inbox and Mailgun talk in both directions?

Yes. Build one flow that starts in Inbox 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 Inbox to Mailgun

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

Inbox triggers: 6
Inbox actions: 7
Mailgun triggers: 8
Mailgun actions: 9

Automation ideas

What you can build with Inbox and Mailgun

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

New Contact in Inbox creates Send Email in Mailgun
Triggers when a new contact is added to your INBOX account (through a form, manual entry, import, or API).
New Bounce Event in Mailgun creates Add Contact to List in Inbox
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Contact in Inbox creates Validate Email in Mailgun
Triggers when a new contact is added to your INBOX account (through a form, manual entry, import, or API).
New Bounce Event in Mailgun creates Create Contact List in Inbox
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Contact in Inbox creates Add Mailing List Member in Mailgun
Triggers when a new contact is added to your INBOX account (through a form, manual entry, import, or API).
New Bounce Event in Mailgun creates Update Contact in Inbox
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun