Now Send Emails Directly From Migma With ESP Integrations

Quick Summary
> Migma now connects directly to Amazon SES, SendGrid, Mailgun, and Resend, so sending happens without leaving the platform. Built-in client testing across Gmail, Outlook, Apple Mail, Yahoo Mail, and others catches layout issues before send, not after. The full workflow now runs create, preview, send, and track in one place, with no export step for teams on a connected ESP.

Your email looks perfect in the builder. Then it hits Outlook and the layout falls apart.

That gap between "looks right" and "sends right" costs teams hours every week. Build the email in one tool. Test it in another. Export it to the ESP. Fix what broke. Repeat.

Migma closes that gap. It now connects directly to Amazon SES, SendGrid, Mailgun, and Resend. Create the email, test it across real clients, and send it, all without leaving the platform.

No CSV exports. No copying HTML into a separate sending tool. Connect your ESP once, select recipients, and send.

This post covers the full workflow, how client testing fits in before you hit send, and how direct ESP sending compares to exporting through Mailchimp or Klaviyo.

What Changed

Migma added direct sending through four email service providers: Amazon SES, SendGrid, Mailgun, and Resend. Client preview testing, which already existed on the platform, is now part of the same send flow instead of a separate step.

New:

• Direct send integration with SendGrid
• Direct send integration with Mailgun
• ESP connection managed inside Migma (no manual API setup outside the platform)

The Four New ESP Integrations

Migma now connects directly to four email service providers. Each serves a different kind of team, and the choice usually comes down to cost structure, deliverability tooling, or how much control the team wants over the sending API.

Amazon SES

SES is the default choice for teams sending high volumes on a tight budget. It has no built-in email design tools of its own, so pairing it with a platform that handles creation and testing closes a real gap for teams already on SES.

SendGrid

SendGrid brings established deliverability infrastructure, including reputation monitoring and inbox placement tools. Marketing teams already using SendGrid for its deliverability tooling now get AI creation and client testing without switching providers.

Mailgun

Mailgun is built for technical teams that treat email as another API to integrate, particularly for transactional and triggered sends. Direct integration means a Mailgun-based team can add AI-assisted design without building a separate creation layer.

Resend

Resend has grown with product-led and startup teams that want a modern developer experience over legacy ESP tooling. Connecting Resend to Migma extends that same expectation to the creation and testing side of the workflow.

What Connecting an ESP Requires

Connecting an ESP to Migma involves authenticating the account, typically through an API key or OAuth depending on the provider, and verifying a sending domain. This is standard practice across ESP integrations and confirms the sender is authorized to send on behalf of the domain.

Built-In Email Client Testing

Before an email sends, Migma previews it across major clients, including Gmail, Outlook, Apple Mail, Yahoo Mail, and others.

Why layout breaks happen

Every email client renders HTML and CSS differently. There's no single standard the way there is for modern browsers.

• Outlook (desktop versions from 2007 onward) uses Microsoft Word's rendering engine, not a browser engine. It ignores common CSS properties like float, position, and max-width, which forces email designers to build with table-based layouts instead of modern CSS.
• Dark mode handling varies by client. Some clients invert light backgrounds automatically, which can turn a white logo transparent or make a light-colored button unreadable against its own background.
• Image blocking is on by default in Outlook and several other clients. Any layout that relies on a background image to hold its structure, rather than a background color as a fallback, collapses when the image doesn't load.
• Apple Mail and Gmail support more modern CSS than Outlook, which means an email that looks correct in one can still break in the other. Testing in only one client gives false confidence.

What a preview catches before send

• Tables that collapse or misalign, usually from padding or width values that one client honors and another ignores
• Font fallback issues, where a custom or web font fails to load and the backup font changes line length enough to break spacing around buttons or images
• Subject lines and preheader text clipped in the inbox list view, which cuts off the message before the recipient opens it
• Broken or missing alt text on images, which matters specifically in clients where images are blocked by default and alt text is the only content the recipient sees
• Color contrast issues introduced by dark mode inversion, where text and background can end up nearly the same color

Why this matters before send, not after

Catching a rendering issue after an email has gone to a full list means the damage is done. A broken layout in Outlook alone can affect a large share of a B2B list, since Outlook remains common in corporate inboxes. Testing inside the same workflow used to build the email means the fix happens before send, not in a follow-up apology email.

The Full Workflow, Step by Step

1. Create the email with AI. Describe the email or start from a prompt, and Migma generates the layout, copy, and design based on the brand's existing colors, fonts, and tone.
2. Preview across major clients. Before anything sends, the email renders across Gmail, Outlook, Apple Mail, Yahoo Mail, and other major clients, so layout issues surface while they're still easy to fix.
3. Send through the connected ESP. Once the email passes preview, it sends directly through the connected Amazon SES, SendGrid, Mailgun, or Resend account. Recipients are selected inside Migma, with no export step in between.
4. Track performance with built-in analytics. Open rates, click rates, and other send performance data come back into the same platform, so results are tied to the email that produced them instead of living in a separate ESP dashboard.

Why the order matters

Each step depends on the one before it. Creating first means the AI has a complete draft to test, not a partial one. Testing before sending means issues get caught while changes are still cheap. Sending before tracking means performance data has something concrete to measure against.

Removing a step, or doing it in a separate tool, is where most email production breaks down today. A layout built in one tool and tested in another can drift between the two, since exporting HTML doesn't always preserve every style. Keeping all four steps in one platform removes that drift entirely.

Why This Matters for Deliverability and Speed

Every handoff between tools is a place for something to break. An email built in a design tool, tested in a separate client-preview tool, then exported into an ESP, passes through three points of failure instead of one.

Formatting breaks most often at the export step. HTML that renders correctly in the design tool doesn't always carry every style through an export into the ESP's editor. A button color, a spacing value, or a font fallback can shift without anyone noticing until the email is already live.

Reducing that to one platform removes the export step entirely. What was tested is what sends, with no conversion in between.

Speed follows the same logic. Time spent moving an email between three tools is time not spent on the email itself. Fewer handoffs means fewer rounds of catching and fixing issues that shouldn't have existed in the first place.

How This Compares to Export-Based Sending

Migma supports two ways to get an email out the door: send it directly through a connected ESP, or export it to a platform like Mailchimp, Klaviyo, or HubSpot. Neither is wrong, but they fit different teams.

Direct ESP send

This path fits teams that already have Amazon SES, SendGrid, Mailgun, or Resend set up and don't want to move their sending infrastructure. Creation, testing, and sending happen in one place. There's no export format to worry about and no risk of styling shifting between tools.

Export to platform

This path fits teams standardized on a platform like Mailchimp or Klaviyo, often because their audience segmentation, automation flows, or reporting already lives there. Migma builds and tests the email, then hands off a finished export. Testing still happens inside Migma before the export, but final send and any platform-specific formatting checks happen after the email leaves Migma.

Choosing between them

The decision usually comes down to where the rest of the marketing stack lives. A team with segmentation and automation built inside Klaviyo has a reason to keep exporting there. A team that only needs an ESP to send, with segmentation and workflow handled elsewhere or not needed at all, has less reason to add an export step.

Conclusion

Building an email, testing it, and sending it used to mean three tools and three chances for something to break. That's no longer necessary.

Migma now connects directly to Amazon SES, SendGrid, Mailgun, and Resend. Client preview testing happens in the same workflow, before send, not after. For teams that already own an ESP relationship, this removes the export step entirely.

The choice isn't between AI email creation and keeping your existing sending infrastructure. Migma now supports both at the same time.

Configure Your ESP Integration

Connect Amazon SES, SendGrid, Mailgun, or Resend to Migma and send your next email without leaving the platform.

Frequently Asked Questions