Skip to content
ConvertKit logoMailgun logo

Connect ConvertKit to Mailgun

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

ConvertKit triggers
12
ConvertKit actions
35
Mailgun triggers
8
Mailgun actions
9

Automation ideas

What you can build with ConvertKit and Mailgun

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

  • Tag added to subscriber in ConvertKit creates Send Email in Mailgun

    Trigger when a tag is added to a subscriber

  • New Bounce Event in Mailgun creates Get Subscriber By Id in ConvertKit

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

  • Tag added to subscriber in ConvertKit creates Validate Email in Mailgun

    Trigger when a tag is added to a subscriber

  • New Bounce Event in Mailgun creates Get Subscriber By Email in ConvertKit

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

  • Tag added to subscriber in ConvertKit creates Add Mailing List Member in Mailgun

    Trigger when a tag is added to a subscriber

  • New Bounce Event in Mailgun creates List Subscribers in ConvertKit

    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 ConvertKit 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.