Webflow has no built-in email marketing, so you connect it to Mailchimp in one of three ways: embed Mailchimp's signup form in a Code Embed element, point a native Webflow form at Mailchimp's subscribe URL, or route submissions through Zapier or Make. Publish the site to test, because custom code doesn't run in preview.
Webflow handles design, CMS content and hosting, but it doesn't do email marketing, audience management or automated campaigns. Form submissions stay in Webflow's own database, with no native way to send them to an email list. So you need a bridge. Webflow's own integration guide describes three, plus a popup option.
Which route fits your site
| Route | Good for | Watch out for |
|---|---|---|
| Embed Mailchimp's form | Quickest setup, posts straight to Mailchimp | Styling clashes with Webflow CSS |
| Native form with a custom action URL | Forms designed in Webflow | Lost success messages and case-sensitive field names |
| Zapier or Make | Tags, conditions, Webflow's own success states | A delay of 30 seconds to 3 minutes |
Route one: embed the signup form
- In Mailchimp, open the audience's signup form, adjust the fields, tags and settings, and copy the generated HTML.
- In Webflow, drag a Code Embed element onto the page and paste the HTML. The form posts directly to Mailchimp.
- Leave the hidden spam-protection field in the code. Removing it breaks spam protection.
- Publish the site and test a signup, since custom code doesn't run in preview mode.
If the subscribe button disappears after publishing, it's usually a CSS class collision: Webflow's global styles override Mailchimp's markup. Rename or scope the clashing classes.
Route two: point a native form at Mailchimp
Build the form in a Webflow Form Block, then set its action attribute to Mailchimp's subscribe URL, the list-manage address for your account. This keeps your design fully in Webflow.
Two things go wrong here. Field names must match Mailchimp's merge tags exactly, and matching is case-sensitive. Get one wrong and the form appears to succeed while the subscriber arrives with empty or incomplete data. And with a custom action URL, Webflow's built-in success and error states don't display, and you have to remove Webflow's email notification destinations, because its submission storage can't run alongside a custom action.
Route three: Zapier or Make
Automation platforms route Webflow form submissions to Mailchimp with tagging, conditional logic and field mapping. Zapier offers nine pre-built templates for the pair. Because the form still submits to Webflow first, your native success and error messages display as normal, and submissions stay in Webflow too.
The trade-off is speed: automation adds a delay of 30 seconds to 3 minutes between a submission and the Mailchimp sync. For a newsletter sign-up that's fine; for an instant welcome email, it's worth knowing.
Popups and the API
For a popup, paste Mailchimp's JavaScript snippet into the site's footer custom code. The popup's design is controlled in Mailchimp, and iframe popups can't be styled from Webflow. For full control over syncing, the Webflow and Mailchimp APIs can be connected directly, but that needs server-side development.
Silent data loss on custom action forms
The Webflow guide to the Mailchimp integration is blunt about route two: pointing a native form at Mailchimp switches off Webflow's success and error messages and its submission storage, and a mismatched field-name case quietly loses data. If you want to keep Webflow's form behaviour, use Zapier or Make and accept the short delay.
Other email platforms on Webflow
Klaviyo's Webflow integration page says there's no native Klaviyo integration either, so every Webflow setup starts with a manual snippet or a connector app. If you're choosing between them, my Klaviyo and Mailchimp comparison helps, and if you're still weighing site builders, here's Webflow versus WordPress.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
My advice for most small sites
If you've no developer, use Zapier or Make: you keep Webflow's form design and messages, and tagging is easy. If you need the fastest possible sync, embed Mailchimp's form and fix any CSS clashes. Only use the custom action URL if you'll check every field name against the merge tags, and always test on the published site.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Does Webflow have a native Mailchimp integration?
The Webflow guide describes connecting through embedded Mailchimp forms, a custom action URL or automation platforms, rather than a built-in link.
Why does my Mailchimp form not show in preview?
Custom code doesn't run in Webflow's preview mode. Publish the site to test it.
Why are subscribers arriving with empty fields?
Field names must match Mailchimp's merge tags exactly, and matching is case-sensitive.
Can I keep Webflow's success message?
Not with a custom action URL. Route through Zapier or Make so the form submits to Webflow first.
How long does Zapier take to sync a signup?
Webflow's guide says automation platforms add a delay of 30 seconds to 3 minutes.