Mailgun Email Template Builder

Q: Do Mailgun recipient variables and template variables work?

Yes. Anything you type into a Temway text block — %recipient.firstname%, %recipient.email%, or any Mailgun variable — passes through untouched, and Mailgun processes it at send time as normal.

Design in Temway, send from Mailgun

Temway is a visual email template builder that connects directly to Mailgun. Compose a responsive email with drag-and-drop blocks, then push it into your Mailgun account as a domain-scoped template — ready to call from your application code or marketing send.

If you’ve been searching for a “Mailgun template builder” that gives you production-grade responsive HTML without hand-authoring markup, this is it. You design; Mailgun keeps doing what it’s good at — routing, delivery, and high-volume transactional send.

Why design in a separate builder?

Mailgun is developer-first — most teams author templates in code or paste HTML straight into the API. Hand-writing Mailgun-ready HTML is where the friction lives:

Responsive columns that drift in Outlook — hand-coded layouts are fragile; a single mistake breaks rendering in Outlook.
Hand-writing email HTML is slow — Mailgun’s templates expect clean, client-safe markup, which is tedious and error-prone to produce by hand.
No single source of truth — every transactional email (welcome, reset, receipt) is authored separately, so brand consistency drifts.
Dark-mode rendering you can’t fully control — logos invert, transparent PNGs get dark halos, brand colors shift.

Every email Temway exports is built to render correctly across Gmail, Outlook, and Apple Mail, with responsive behavior already handled. You compose visually; the output is clean HTML that drops straight into a Mailgun template.

This isn’t about replacing Mailgun — it’s about giving your team a faster, more reliable way to design the transactional and marketing emails Mailgun sends.

How the Mailgun integration works

Connect your Mailgun account once from your Temway workspace’s integration settings using your API key. Mailgun templates are scoped to a sending domain, so Temway captures your first active domain at connect time. When your email is ready, choose Push to Mailgun. Temway renders the final, inbox-ready HTML and creates a new template on that domain.

Lands as a domain-scoped template with an initial active version — ready to reference by template name from your application code.
Region auto-detected — Mailgun has separate US and EU hosts. Temway tries US first and falls back to EU on auth, so you don’t have to pick a region when connecting.
Authenticates with your Mailgun API key.
Client-safe output means the pushed HTML renders consistently across Gmail, Outlook, Apple Mail, and the rest.
Credentials encrypted at rest — your API key is never displayed again after you connect.

Mailgun-specific details that just work

Because Temway pushes raw HTML into a Mailgun template and Mailgun processes its own recipient variables at send time, a few things work exactly the way Mailgun users expect:

Recipient variables pass through. Paste %recipient.first_name%, %recipient.email%, or any Mailgun template variable into a Temway text block — it renders into the HTML untouched and resolves normally when Mailgun sends.
Versioned by default. Your first push creates the template with an initial active version. Re-push from Temway to iterate — Mailgun keeps version history you can roll back to.
Design-only by design. Temway never touches your routes, domains, suppression list, or send configuration. Those stay entirely in Mailgun — Temway only creates the template; your application decides when to fire it.

Start from a Mailgun-ready template

Don’t begin from a blank canvas. Browse the template gallery for responsive, transactional-friendly starting points — then customize the branding, copy, and layout in Temway before pushing to your Mailgun domain.

Frequently asked questions

Why does Temway scope the template to a domain? Because Mailgun does — Mailgun templates live under a specific sending domain. Temway captures your first active domain at connect time and uses it for the push. If you have multiple domains, reconnect with the one you want.

Do Mailgun recipient variables and template variables work? Yes. Anything you type into a Temway text block — %recipient.first_name%, %recipient.email%, or any Mailgun variable — passes through untouched, and Mailgun processes it at send time as normal.

Does Temway sync my Mailgun routes, domains, or suppression list? No. Temway is design-and-push only. Routes, domains, suppression management, and send settings live entirely in Mailgun. Temway creates a template; your application code decides who receives it.

What Mailgun plan do I need? You need a Mailgun API key with at least one active sending domain on your account. Beyond that, send volume and feature access depend on your Mailgun plan (Flex, Foundation, etc.) — check Mailgun’s current pricing for specifics; that’s a Mailgun question, not a Temway one.

Get started

Connect Mailgun from your workspace integration settings, then push your first email. The ESP integrations documentation covers the full walkthrough.