Can KrispCall and Mailgun talk in both directions?

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

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

KrispCall triggers: 5
KrispCall actions: 4
Mailgun triggers: 8
Mailgun actions: 9

Automation ideas

What you can build with KrispCall and Mailgun

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

New Voicemail in KrispCall creates Send Email in Mailgun
Trigger when a new voicemail is received.
New Bounce Event in Mailgun creates Add Contact in KrispCall
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Voicemail in KrispCall creates Validate Email in Mailgun
Trigger when a new voicemail is received.
New Bounce Event in Mailgun creates Delete Contacts in KrispCall
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Voicemail in KrispCall creates Add Mailing List Member in Mailgun
Trigger when a new voicemail is received.
New Bounce Event in Mailgun creates Send SMS in KrispCall
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun