Get Started
Integrations
Docs chevron_right Integrations chevron_right Export to Mailchimp

Export to Mailchimp

Design in EmailFlow AI, send from Mailchimp. Connect your Mailchimp account once, then push any finished email straight into your Mailchimp template library — the exact final HTML the AI Design Studio produced, with nothing rewritten on the way out.

Connecting Mailchimp

Open Integrations in the sidebar and click Connect on the Mailchimp card. You are sent to Mailchimp's own authorization screen; log in, approve access, and you are returned here with the connection live. There are no API keys to copy — the whole flow is OAuth, and the token Mailchimp issues is stored encrypted at rest.

The connection is tied to the specific Mailchimp account you approve, including its datacenter, so exports always land in the right account. Mailchimp access tokens do not expire; the connection stays live until you disconnect it here or revoke the app inside Mailchimp.

Pushing an email

From Email Templates, open the more_vert menu on any template card and choose Push to ESP — or use the Push to ESP button in the AI Design Studio's top bar while you are editing. Pick Mailchimp from the provider list and the export is queued.

emailflow.ai/rui/email-templates
The Push to ESP dialog listing Mailchimp, Klaviyo, and HubSpot: connected providers show a Push button, unconnected ones a Connect link
Pick a destination — connected providers push immediately, the rest link to setup.

The export runs in the background and the dialog updates itself: a spinner while the push is in flight, then a link to open the result in Mailchimp. Your email arrives as a new entry in Mailchimp → Templates under the same name it has here, ready to drop into any Mailchimp campaign.

code
What Mailchimp receives is the same final HTML as Download HTML — inlined, email-client-safe markup produced by one shared export pipeline. What you previewed here is what Mailchimp gets, byte for byte.

The export log

Every push — successful or not — is recorded on the connection's Manage page (Integrations → Mailchimp → Manage): the template, when it ran, its status, a link to the artifact in Mailchimp, and for failures the provider's error message verbatim, so you never have to guess what the other side rejected.

emailflow.ai/rui/integrations/mailchimp
The Manage connection page for an ESP: connection status card with Disconnect, above a table of past exports with status badges, timestamps, and links to the exported artifact
The Manage page — connection health on top, full export history below.

Troubleshooting

  • The connection shows an error badge. Mailchimp rejected our token — usually because the app's access was revoked inside Mailchimp. You also get an in-app notification when this happens. Click Reconnect on the Manage page to run the OAuth approval again; history is kept.
  • An export failed. The log row carries Mailchimp's own error text. Transient vendor errors are safe to retry — just push again.
  • Push to ESP asks me to upgrade. Template export is HTML egress and follows the same plan flag as Download HTML; it is available on paid plans.

Disconnecting from the Manage page deletes the stored token immediately — nothing keeps working in the background — while your export history stays visible.