Skip to content
Sender logoMailgun logo

Connect Sender to Mailgun

Move data between Sender 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.

Sender triggers
7
Sender actions
7
Mailgun triggers
8
Mailgun actions
9

Automation ideas

What you can build with Sender and Mailgun

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

  • New Campaign in Sender creates Send Email in Mailgun

    Fires when a new campaign is created in Sender

  • New Bounce Event in Mailgun creates Add / Update Subscriber in Sender

    Triggers when an email permanently fails to deliver (hard bounce) in Mailgun

  • New Campaign in Sender creates Validate Email in Mailgun

    Fires when a new campaign is created in Sender

  • New Bounce Event in Mailgun creates Create Campaign in Sender

    Triggers when an email permanently fails to deliver (hard bounce) in Mailgun

  • New Campaign in Sender creates Add Mailing List Member in Mailgun

    Fires when a new campaign is created in Sender

  • New Bounce Event in Mailgun creates Unsubscribe Subscriber in Sender

    Triggers when an email permanently fails to deliver (hard bounce) in Mailgun

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

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