Messaging and email

Mailgun

Connect Mailgun to send transactional email from workflows, with US and EU API regions, text and HTML bodies, and webhook signing key storage.

01 / Workflows

What you can automate.

The Mailgun connection stores API key, sending domain, region, and optional webhook signing key. The current agent module sends email through the Mailgun REST API.

  1. Send workflow-generated emails through a Mailgun domain.
  2. Use text or HTML bodies with sender, CC, BCC, reply-to, and tags.
  3. Keep inbound webhook signing configuration with the provider connection.

02 / Capabilities

What it covers.

The full reference, with connection types, is in the Mailgun docs.

Capabilities

  • Send email
  • US and EU API regions
  • Text and HTML body support
  • CC, BCC, reply-to, and tags
  • Webhook signing key storage

Data handled

  • Recipients
  • Email bodies
  • Headers
  • Message IDs

03 / Availability

In every edition.

Mailgun is a standard integration, included in Cloud, Enterprise and the open-source engine. Compare plans

  • Open-source engineAGPL-3.0, run and operate it yourself.Included
  • CloudWe host and manage your instance.Included
  • EnterpriseYour cloud or on-premises, supported by our team.Included

04 / Questions

Common questions.

Is Mailgun included in my plan?

Yes. Mailgun is a standard integration, included in Cloud, Enterprise and the open-source engine.

How is it set up?

A connection stores the Mailgun credentials once for your instance. Workflow steps that use it declare that connection, and the runtime denies anything else.

Can a person approve before anything is written?

Yes. A workflow holds an exception for approval and continues only after the person decides. The run keeps the source, the decision, who made it, and the response together.

More in Messaging and email

Put Mailgun to work.

Start with a paid pilot of one real process. Our team builds and runs it, live in two weeks once access is in place.

Discuss your process

All product names, logos and brands are the property of their respective owners and are used here in good faith, only to identify the systems Runtara connects to. Their use does not imply any affiliation with, or endorsement or sponsorship by, those owners.