How to Connect Mailchimp to Webflow: : 3 Methods in 2026

Sanket vaghani
How to Connect Mailchimp to Webflow: : 3 Methods in 2026

Table of content

Free Website Audit by Experts

Actionable insights to improve SEO, speed, and conversions

Request Free Audit

Key takeaways

There are three ways to connect Mailchimp to Webflow. The simplest is to embed Mailchimp's own signup form in Webflow. For a native-looking Webflow form, connect it to Mailchimp with an automation tool like Zapier or Make so submissions create subscribers. The third option uses a Webflow app or direct action where available. If submissions show in Webflow but not Mailchimp, the connection between the two isn't set up Webflow stores the submission but doesn't forward it on its own.

Getting Webflow form submissions into Mailchimp is one of those tasks that's genuinely five minutes once you know the path, and a frustrating afternoon when you don't. The confusion is almost always the same: people build a Webflow form, see submissions arriving in Webflow, and assume Mailchimp is getting them too. It isn't Webflow stores form data, but it doesn't push it to Mailchimp unless you connect the two.

There are three ways to make that connection, and the right one depends on whether you want the simplest setup or the most control over design and automation. Here's each method step by step, the field-mapping and opt-in details that trip people up, and the fix for the most common problem of all.

How Webflow and Mailchimp Actually Connect:

Webflow and Mailchimp don't have a deep, built-in, one-click link the way some platforms do. Instead you're choosing how the data gets from a form to your Mailchimp audience:

  • Embed Mailchimp's form → Mailchimp handles everything, styling included.
  • Webflow form + automation (Zapier/Make) → your on-brand form, connected behind the scenes.
  • Webflow app / direct action → a native-ish option where available

Understanding that upfront saves the classic mistake of expecting submissions to appear in Mailchimp automatically. Now the methods.

Method 1: Embed a Mailchimp Form (Simplest)

If you just want a working signup and don't need it to perfectly match your design, embed Mailchimp's form directly. It's the fastest route and needs no third-party tool.

  1. In Mailchimp, go to Audience → Signup forms → Embedded forms and build your form with the fields you want.
  2. Copy the generated embed code.
  3. In Webflow, drag an Embed element where you want the form and paste the code in.
  4. Publish. Submissions go straight into your Mailchimp audience no extra connection needed.

Trade-off: the form's styling comes from Mailchimp, so it won't perfectly match your Webflow design without extra CSS. Fastest to set up, least control over the look. Good for a footer signup or a quick newsletter box.

Method 2: Connect a Webflow Form with Zapier (Most Control)

This is the route most teams actually want a native Webflow form that looks like the rest of your site, wired to Mailchimp behind the scenes.

  1. Build your form in Webflow as normal, with the fields you want (at minimum an email field; add name, company, or interests if you segment).
  2. In Zapier, create a Zap with Webflow → New Form Submission as the trigger and connect your Webflow site and the specific form.
  3. Add Mailchimp → Add/Update Subscriber as the action, connect your Mailchimp account, and choose the target audience.
  4. Map the Webflow fields to Mailchimp fields email to email, first name to first name, and any custom fields to their Mailchimp merge fields.
  5. Optionally add tags or a group so you know where the subscriber came from.
  6. Turn the Zap on and submit a real test. The subscriber should appear in Mailchimp within a minute.

This keeps your form fully on-brand and gives you room to grow you can later add steps like tagging subscribers by source, notifying your team, or updating a CRM at the same time. Make (formerly Integromat) works the same way if you prefer it, and tends to be cheaper at higher volumes.

Method 3: Connect a Webflow form Directly with Mailchimp's Code

Mailchimp can also connect to a native Webflow form using its own connection and action code no automation tool in between. The flow is:

  1. In Webflow, add the required connection code to your Site Settings (in the custom code area).
  2. In Webflow, add the required connection code to your Site Settings (in the custom code area).
  3. Generate Mailchimp's form action code and point your Webflow form's action at it, so the form posts submissions to Mailchimp.
  4. Match the form field names to what Mailchimp expects, then test and publish.

This keeps a native, on-brand Webflow form while sending straight to Mailchimp without Zapier. It's a little fiddlier to wire up than a Zap (the field names have to line up exactly), but it avoids a third-party subscription. Also check Webflow's Apps for a current Mailchimp option, which can make this even simpler. Our overview of Webflow apps and integrations covers the wider picture.

Mapping Fields and Double Opt-in (Where Signups Quietly Break)

Two details cause most "it's not working" tickets.

Field mapping. Make sure email maps to email and any custom fields (first name, company, interests) line up with the matching Mailchimp merge fields. If a required merge field isn't mapped or is empty, Mailchimp rejects the record and the subscriber never appears even though Webflow shows a successful submission.

Double opt-in. If your Mailchimp audience has double opt-in turned on, new subscribers receive a confirmation email and don't count as subscribed until they click it. This is often why a "successful" signup doesn't show as an active subscriber it's working exactly as designed, just waiting on confirmation. Decide deliberately whether you want double opt-in on (better list quality, fewer confirmed subscribers) or off (more subscribers, less verification).

Troubleshooting: Subscribers Not Syncing

The classic problem: the form submits fine in Webflow, you can see the entry in your form submissions, but nothing lands in Mailchimp. Work down this list and you'll find it:

  • No connection exists. This is the number one cause. Webflow stores submissions but doesn't forward them anywhere by itself. If you haven't set up an embed, a Zap/scenario, or an app action, there's simply nothing carrying the data across.
  • The Zap or scenario is off, or its email field isn't mapped.
  • Double opt-in is holding the subscriber in "pending" until they confirm.
  • A required Mailchimp merge field is empty, so Mailchimp rejects the record.
  • Wrong audience selected - the subscriber went to a different Mailchimp audience than the one you're checking.
  • Duplicate email - Mailchimp updates rather than re-adds an existing subscriber, so it may look like "nothing happened."

It's rarely a mystery once you remember that Webflow doesn't push data on its own.

Which Method Should you Use?

  • Just need signups fast, styling isn't critical? Embed the Mailchimp form (Method 1).
  • Want an on-brand form and room to automate? Webflow form + Zapier or Make (Method 2). This is the right default for most businesses.
  • Have a native app option available? Use it (Method 3), with Zapier as the fallback.

If you're connecting several tools Mailchimp, a CRM, a scheduler like Calendly and want it done cleanly and reliably across the whole site, that's the kind of setup we handle as part of a build. Bring it to us as your Webflow development agency and we'll wire the lead flow end to end.

FAQs

1. Does Webflow integrate with Mailchimp natively?

You can embed a Mailchimp form directly, and depending on your plan and available apps there may be a direct action. For a native-looking Webflow form connected to Mailchimp, most teams use Zapier or Make.

2. Why aren't my Webflow subscribers showing in Mailchimp?

Usually because no connection is forwarding the data Webflow stores submissions but doesn't send them to Mailchimp on its own. Check that your embed, Zap, or app action is set up, your email field is mapped, and double opt-in isn't holding subscribers as pending.

3. Do I need Zapier for Mailchimp and Webflow?

Not if you embed Mailchimp's form or use an available native app action. You need Zapier (or Make) when you want a native-looking Webflow form to create Mailchimp subscribers automatically.

4. Can I add subscribers to a specific Mailchimp audience or group from Webflow?

Yes. With Zapier or Make you choose the target audience and can assign tags or groups, which is how you segment subscribers by where they signed up.

5. Is Zapier or Make better for connecting Webflow to Mailchimp?

Both work well. Zapier is simpler to set up; Make offers more complex logic and is often cheaper at higher volumes. For a straightforward newsletter signup, either is fine.

Sanket vaghani

Sanket Vaghani has 8+ years of experience building designs and websites. He is passionate about building user centric designs and Webflow. He build amazing Webflow websites and designs for brands.

AI in Modern Web Design: Tools, Benefits & Future Trends (2026)

AI in Modern Web Design: Tools, Benefits & Future Trends (2026)

Read how AI is changing modern web design in 2026. From AI design tools to personalization and automation, learn how designers and agencies are building smarter websites.

Webflow vs Figma (and Figma Sites): Which One Builds Real Websites in 2026?

Webflow vs Figma (and Figma Sites): Which One Builds Real Websites in 2026?

Figma designs, Webflow publishes, but Figma Sites blurs the line. Here's Webflow vs Figma and Figma Sites compared, plus how the Figma-to-Webflow workflow fits.

Webflow vs Contentful: Which CMS Is Right for You in 2026?

Webflow vs Contentful: Which CMS Is Right for You in 2026?

Webflow vs Contentful: a visual all-in-one vs headless CMS, pricing, features, who each fits, and when to move from one to the other. A clear 2026 verdict.

Talk to Webflow Expert

Partner with a Webflow Agency for your Webflow website.

Quick Turnaround. No Contracts. Cancel Anytime. Book a 30 minutes consulting call with our expert.