Can Vapi and Mailgun talk in both directions?

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

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

Vapi triggers: 0
Vapi actions: 4
Mailgun triggers: 8
Mailgun actions: 9

Automation ideas

What you can build with Vapi and Mailgun

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

New Bounce Event in Mailgun creates Create Call in Vapi
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Bounce Event in Mailgun creates Get Call in Vapi
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Bounce Event in Mailgun creates Update Assistant in Vapi
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Complaint Event in Mailgun creates Create Call in Vapi
Triggers when a recipient reports an email as spam in Mailgun