Mailchimp Webflow Integration

Your signup form looks right and the site is live. But no subscribers show up in Mailchimp. Or the success message never appears. Or the Webflow notification emails your sales team relied on have stopped coming in. The connection is usually not broken. It was set up with a method that doesn't fit what has to happen after someone clicks submit.

The short answer: a Webflow Mailchimp integration doesn't need an app. You don't install a Webflow app or a Mailchimp app. You point a Webflow form at the action URL from Mailchimp's embedded form, set the method to POST and give each field the name of its Mailchimp merge tag (EMAIL, FNAME, LNAME). If you also need tags, routing or team notifications, use Zapier, Make or the Mailchimp API.

Most tutorials show one copy-paste method and skip the trade-offs. This guide starts with a decision instead. Work out what has to happen after submit: which audience the contact lands in, which tag they get, who on your team is notified and what consent is recorded. Then pick the method that delivers it.

One warning before you start. Some guides still tell you to use Webflow Logic. Webflow shut Logic down on June 27, 2025, and its Logic sunset notice in the Webflow Help Center tells users to rebuild their flows in tools like Zapier or Make. If a tutorial opens the Logic panel, close the tab.

Below you'll find everything a working Mailchimp Webflow integration needs: the prerequisites, a way to choose between four methods, numbered steps for each, field mapping, tagging, testing and a troubleshooting list for when signups go missing.

What you need before you start

Check these before you touch a form setting. Most failed Webflow Mailchimp integrations skip one of them.

• A Mailchimp account with at least one audience. An audience is Mailchimp's word for a contact list. Every signup lands in exactly one audience.
• A Webflow form with a required email input. Webflow's help article Add new subscribers to Mailchimp from your site lists a Form Block with a required input of type Email as a prerequisite. If you're new to forms, start with our guide to Webflow forms.
• Your Mailchimp plan and its limits. Since January 2026 the Free plan covers 250 contacts and 500 sends a month, with a daily limit of 250, according to Mailchimp's pricing and plan overview. Free accounts must also show the Mailchimp Referral badge on embedded forms. Limits change, so check mailchimp.com/pricing before you plan around them.
• A paid Webflow plan if you'll embed code. Method 2 uses the Code Embed element, which the Webflow Help Center says is only available on sites with an active Site plan or users with an active Workspace plan.
• Your opt-in model and consent text. Decide on single opt-in (contacts are added right away) or double opt-in (they confirm by email first), and what consent wording the form needs. That's a legal question, not a technical one. Agree it with whoever owns privacy in your company before you go live.

Which Webflow Mailchimp integration method should you use?

Use the native form action for a simple, on-brand newsletter form. Use the Mailchimp embed when you need Mailchimp's own features, such as GDPR fields or groups. Use Zapier or Make when you need tags, routing to several audiences, or Webflow notifications alongside Mailchimp. Use the API for multi-step forms or custom logic.

Answer four questions first:

• Does the form need to look exactly like the rest of your site? If yes, keep a native Webflow form (Method 1, 3 or 4).
• Does sales need an email when someone submits? A custom action turns off Webflow's form notifications, so you need Method 3 or 4.
• Do you segment by page or interest? Tags and groups push you toward Method 3, or Method 2 for groups.
• Does one form feed more than one audience? One action URL is one audience. Conditional routing needs Method 3 or 4.

Here's how the four Webflow Mailchimp integration methods compare:

• Method 1, native form action: keeps your Webflow design. Loses Webflow form submissions and notification emails. Tags are unreliable and groups don't work. One audience per form. No extra cost. Maintained by whoever edits the site.
• Method 2, Mailchimp embed: uses Mailchimp's markup and styling unless you restyle it. Submissions go to Mailchimp, not Webflow. Supports auto-applied tags and preselected groups. One audience per form. Needs a paid Webflow plan for Code Embed. Maintained in Mailchimp, then re-pasted into Webflow.
• Method 3, Zapier or Make: keeps your Webflow design, submissions and notifications. Full tag support and routing to several audiences. Adds a paid automation subscription. Maintained by someone who owns the automation account.
• Method 4, Mailchimp API: keeps everything, with tags, groups and any routing logic you can describe. Costs a developer build plus hosting for a small server function. Maintained by a developer.

Three facts drive most of this. First, Webflow's Mailchimp Forms integration page states that adding a Mailchimp action URL means you lose Webflow's native form notification emails. Second, each Webflow form connects to one action URL, which is one audience. Third, Webflow's blog post How to connect a Webflow form to Mailchimp explains that Mailchimp Interest Groups don't work as standard field names you can send through a direct POST.

Zapier and Make solve those limits, but they add a subscription and a short processing delay between submit and Mailchimp. Check Zapier's pricing against your monthly signup volume before you commit.

Method 1: Connect a native Webflow form with Mailchimp's action URL

Best for: newsletter and content signups where design consistency matters. This is the simplest Webflow Mailchimp integration: no middleware and no extra subscription.

Step 1: Get the form action URL from Mailchimp

• Create an embedded form in Mailchimp. Webflow's help article Add new subscribers to Mailchimp from your site describes the path as Audience > Signup forms > Create embedded form. Mailchimp's help doc Create and Customize Embedded Signup Forms puts it under Forms > Other forms > Embedded form. Mailchimp moves its menus often, so use whichever label your account shows.
• Name the form, choose the audience and click Continue.
• In the generated code, press Cmd + F (Mac) or Ctrl + F (Windows) and search for form action.
• Copy the URL between the quotes. It contains u= (your account) and id= (your audience). Keep the https:// at the start. Webflow's blog warns that leaving it out breaks the connection.

Step 2: Point your Webflow form at Mailchimp

• In the Designer, select the Form Block and open Element settings > Form settings.
• Change Send to from Webflow to Custom action.
• Paste the Mailchimp URL into Action.
• Set Method to POST. A form left on GET fails without an error, and it's one of the most common reasons nothing reaches Mailchimp.

Step 3: Match every field name to a Mailchimp merge tag

Mailchimp only reads a field when its Name matches a merge tag exactly. The Webflow Help Center is explicit: the names must match, in capitals.

• Email input → Name: EMAIL → Mailchimp field: Email Address
• First name input → Name: FNAME → Mailchimp field: First Name
• Last name input → Name: LNAME → Mailchimp field: Last Name
• Custom field, for example Company → Name: the exact merge tag Mailchimp shows, such as COMPANY → Mailchimp field: the audience field you created

Webflow's default form has a single Name field. Split it into two inputs named FNAME and LNAME, or rename it FNAME if first names are enough. For any custom field, add it to your Mailchimp audience fields first, then copy its merge tag into the Webflow field's Name. To see every tag Mailchimp expects, search the embed code for name=.

Step 4: Add tags or source tracking with hidden fields (optional)

Mailchimp's embedded form builder can tag everyone who signs up through that form automatically. One documented approach, from Flow Camp's tutorial How to Integrate Mailchimp with Webflow Forms, copies that behavior into a Webflow form: add a Code Embed inside the form containing a hidden input named tags, with the tag value taken from the builder's code.

Be careful here. Webflow's own blog says the direct action method doesn't support tags. The sources disagree, so test on a test audience first. If the tag doesn't appear on the contact, use Method 3.

Tracking the source page is more reliable. Mailchimp's help doc Determine Webpage Signup Location works like this:

• Create a hidden text field in your Mailchimp audience, for example with the merge tag SIGNUP.
• Prefill it per page by adding &SIGNUP=value to the end of the action URL, such as &SIGNUP=Homepage. A hidden Webflow input named SIGNUP with a fixed value does the same job.
• Build segments in Mailchimp on that field. Text-field segments match exact values, so keep your values consistent: "pricing-page" and "Pricing-Page" can end up in different segments.

How we'd build it: make the signup form a Webflow component with the source value as a property, or bind it to a field in your CMS collections. Every new landing page then reports its own source, and marketing never has to edit code.

Step 5: Publish, test and fix what happens after submit

• Publish, then test on the live site. Custom form actions don't run in Designer preview.
• Submit with an email address you control. If double opt-in is on, the contact only appears after you click the confirmation email. Check spam.
• Expect Mailchimp to handle the response. Webflow's blog warns that your Webflow success state won't behave like it does on a normal form, and visitors can end up on Mailchimp's hosted confirmation page.
• Send them back to your site instead. Mailchimp's thank-you page guide places the setting under Forms > Settings: edit the Basic Subscribe Form, open the Success step and redirect to an external URL, such as a thank-you page on your Webflow site. Confirm the current menu path in your account, because Mailchimp renames these screens regularly.
• Open Audience > All contacts and check that the test contact is there with every field filled.

Method 2: Embed Mailchimp's form code in Webflow

Best for: Mailchimp-specific features such as GDPR permission fields or interest groups, and forms your marketing team wants to manage inside Mailchimp.

• In Mailchimp, open the embedded form builder. Mailchimp's Create and Customize Embedded Signup Forms doc lists four menus: Form Fields, Settings, Tags and Referral Badge. Set the fields, auto-apply any tags and choose the badge (Free accounts must keep it, per Mailchimp's pricing page).
• Click Continue and copy the code.
• In Webflow, drag a Code Embed element where the form should appear and paste the code. See our guide to custom code in Webflow if you haven't used embeds before.
• Publish the site.
• Submit a test signup on the live page and check the contact in Mailchimp.

Putting every signup from a page into a group. Mailchimp's help doc Automatically Add Subscribers to a Group at Signup shows how. Create a checkbox group, find its input in the embed code and add the word checked before the closing bracket. Then hide the group's container so visitors can't see or untick it. Repeat this for each page that needs a different group.

Watch for these pitfalls:

• Style and script clashes. Mailchimp's Troubleshooting the Embedded Signup Form guide explains that the embed uses its own CSS and jQuery validation, and either can conflict with your site's styles and scripts. A missing Subscribe button or success message usually means a conflict.
• It won't match your design system. The form ignores your Webflow classes until you restyle it with custom CSS.
• Edits don't sync. Mailchimp's Add an Embedded Signup Form to Your Website doc says that when you change an embedded form, code already pasted on your site doesn't update. Copy the new code and replace the old embed every time.
• The size limit is rarely a problem. A Code Embed holds up to 50,000 characters, far more than a Mailchimp form needs.

Stop fake signups with reCAPTCHA. Turn it on in your Mailchimp form settings. If the form is already live, Mailchimp's help center says you have to generate new embed code and replace the old code for reCAPTCHA to work.

Method 3: Connect Webflow and Mailchimp with Zapier or Make

Best for: B2B sites that need to keep Webflow submissions and team notifications, tag contacts by form or page, or route signups to different audiences.

The key difference: leave your Webflow form on Send to: Webflow. Webflow keeps the submission, sends its notification email and shows your own success state. Zapier picks up the submission and passes it to Mailchimp.

• Publish the site and submit one test entry. The Webflow Help Center notes the form needs at least one submission before Zapier can connect to it.
• In Zapier, create a Zap with the trigger Webflow: New Form Submission. Connect your account, then choose the site and the form.
• Add the action Mailchimp: Add/Update Subscriber. Webflow's blog post How to connect a Webflow form to Mailchimp recommends it over plain Add Subscriber because it checks for an existing contact and updates it rather than failing or duplicating.
• Choose the audience and map the fields: email to Subscriber Email, then the name and custom fields to their merge tags.
• Set the status: Subscribed for single opt-in, Pending for double opt-in.
• Add tags, either fixed text such as "pricing-page" or a value from a hidden form field.
• Test the action, check the contact in Mailchimp, then publish the Zap.
• After launch, check Zap History for failed runs. Each failure shows what went wrong, usually a missing required field.

Make works the same way with its own Webflow and Mailchimp modules: a Webflow form-submission trigger followed by a Mailchimp add or update action. Pick whichever tool your team already pays for.

Cost: count the automation plan in the total cost of the setup. Your volume decides the tier, so check current Zapier pricing or Make pricing before choosing. Our Webflow Zapier integration page covers the wider setup, and the same pattern feeds a spreadsheet through the Webflow Google Sheets integration.

If you used Logic before: Webflow's Logic sunset notice in its Help Center says forms connected to Logic flows became standard Webflow forms on June 27, 2025, and the flows themselves have to be rebuilt in Zapier, Make or a similar tool. If a Logic flow once sent your signups to Mailchimp, submit a test entry today. Your form may have been saving to Webflow only for months.

Method 4: Use the Mailchimp Marketing API

Best for: multi-step forms, lead qualification, routing by field value, or syncing to a CRM as well as Mailchimp. It's the most flexible Webflow Mailchimp integration, and the most work to run.

Webflow's Mailchimp integration page describes the pattern:

• A Webflow webhook fires on every form submission and sends the data to your endpoint.
• A serverless function or small middleware validates the data and checks the webhook signature.
• The function calls Mailchimp's POST /lists/{list_id}/members endpoint with the subscription status, merge fields, tags and interest groups in a single request.
• Duplicates are handled with a PATCH request or the update_existing parameter, so returning contacts are updated instead of rejected. Check the list members reference for the current request format before you build.

Never put your Mailchimp API key in front-end code. Anyone who views your page source can read it. Webflow's integration page states its front end can't store API keys securely, which is why this method always needs a server layer.

What it costs you: a developer to build it, somewhere to host the function, and someone to maintain it when either API changes. It's worth it when the form drives revenue decisions, for example routing enterprise leads to sales and everyone else to a nurture track, or when the same submission must also reach your CRM. For a newsletter box, it's overkill.

Why aren't my Webflow signups showing up in Mailchimp?

Most broken Webflow Mailchimp integrations come down to one of four things: a field name that doesn't match the merge tag, the method set to GET, a missing https:// in the action URL, or double opt-in waiting for a confirmation click. Work through the list below from top to bottom.

• No contacts arrive at all. Cause: field names don't match merge tags, Method is GET, or the action URL is incomplete. Fix: rename fields to EMAIL, FNAME and LNAME in capitals, set POST and re-copy the full URL including https://.
• Contacts appear late or not at all. Cause: double opt-in. Fix: the contact must click Mailchimp's confirmation email first. Check the spam folder.
• The form fails once reCAPTCHA is on. Cause: both platforms checking at once. Fix: with single opt-in and Webflow reCAPTCHA enabled, disable Mailchimp's reCAPTCHA for single opt-in forms. With double opt-in, the Webflow Help Center says both can stay on.
• Visitors land on a Mailchimp page. Cause: Mailchimp handles the response on a custom action. Fix: set a redirect to your own thank-you page in Mailchimp's form settings.
• Webflow notification emails stopped. Cause: a custom action disables them, as Webflow's Mailchimp integration page confirms. Fix: switch to Method 3 with the form on Send to: Webflow.
• Visitors are sent to Mailchimp's hosted form with alerts. Cause: a required field is hidden or deleted from the form. Fix: per Mailchimp's Troubleshooting the Embedded Signup Form guide, find the field marked required and hidden, then make it optional or add it to the form.
• "Too many subscribe attempts for this email address." Cause: browser autofill filling Mailchimp's hidden anti-spam field. Fix: Mailchimp's help center suggests turning off autofill and trying again in about five minutes.
• Duplicate contacts. Cause: Zapier set to Add Subscriber. Fix: use Add/Update Subscriber.
• Data lands in the wrong fields. Cause: forms in the same project sharing field names. Fix: BRIX Templates' guide How to integrate Webflow forms with Mailchimp recommends unique field names across the forms in a project.

One known issue has no clean fix. Webflow's blog post How to connect a Webflow form to Mailchimp, last updated in April 2026, reports that Firefox's Enhanced Tracking Protection can block direct POST submissions to Mailchimp, from native form actions and embedded forms alike, with no reliable workaround. Browser behavior changes, so check the post for the current status. For high-stakes forms such as demo requests, Webflow recommends Zapier, which sends the data from a server instead of the visitor's browser.

Can one Webflow form send subscribers to different Mailchimp audiences?

Not with the native action. One action URL equals one audience. You have three options:

• Separate forms, each with its own action URL. Simple, but every form is another thing to maintain.
• One audience, segmented by tags or hidden fields. We recommend this for most B2B teams. Mailchimp's audience guide recommends one primary audience organized with tags and segments, and counts a contact who sits in two audiences as two contacts when it bills you.
• Zapier, Make or the API for conditional routing, for example by the value of a dropdown.

Can I keep Webflow form notifications and send to Mailchimp?

Not with a custom action. Webflow's Mailchimp Forms integration page confirms you lose the native notification emails as soon as the form sends to a Mailchimp action URL. To keep both, leave the form on Send to: Webflow and pass submissions to Mailchimp with Zapier or Make (Method 3). Your team keeps its alerts, Webflow keeps a copy of every submission and Mailchimp gets the contact.

Is Mailchimp the right tool for a B2B Webflow site?

Mailchimp works well for newsletters, content signups and event invites: one audience, a handful of tags, regular campaigns. It's a good fit when the goal is staying in touch.

It's a weaker fit when sales needs lead routing, deal stages and a clean handoff from marketing. A CRM does that job better. See our guides to the Webflow HubSpot integration, the Webflow Salesforce integration and the Webflow Pipedrive integration. If you want deeper marketing automation, compare the Webflow ActiveCampaign integration and the Webflow Klaviyo integration.

Also check the plan maths. The Free plan's 250 contacts and 500 monthly sends suit a test or a very small list. Paid plans are priced by contact count, so check Mailchimp's pricing page against your expected list size. All our integration guides are collected on the Webflow integrations hub.

How Overflow builds Webflow Mailchimp integrations

The old way: someone pastes an action URL into a form on one page, then another, then copies the form for a campaign. Nobody writes down which form feeds which audience. Six months later, signups are going missing and nobody knows where to start looking.

The Overflow way: we treat every Webflow Mailchimp integration as part of the marketing system, not a setting someone pastes in. On every build:

• Every form is mapped to an audience, its tags and its source value before anything is built.
• Consent rules and the opt-in model are agreed with whoever owns privacy.
• The method fits what has to happen after submit, with a tested fallback for when that fails.
• Signup forms are built as components, so new pages inherit the right setup.
• Marketing gets documentation it owns after handover, so it can add forms without calling a developer.

Who's behind this guide. Overflow is a small senior team. Niels Voshol leads strategy, SEO and AI Search. Jort Steinebach, our Certified Webflow Developer, builds the Webflow side: forms, components and CMS architecture, across more than 40 Webflow sites. Every step in this guide follows Webflow's and Mailchimp's own documentation, cited where it's used, so you can check each claim at the source.

Overflow is an official Webflow Certified Partner. When we move sites from WordPress or HubSpot, existing integrations move with them as part of the WordPress to Webflow migration. Read more on how Webflow integrations work, or see what our Webflow agency work covers.

Want your Webflow forms connected to Mailchimp and documented so your team can run them? Let's talk.

FAQ

Is there an official Mailchimp app for Webflow?

Webflow's Mailchimp integration page states that Mailchimp doesn't have an official app in the Webflow Apps Marketplace. Instead it describes three routes: the native form action, Mailchimp's embed code, and the API. Third-party apps change, so check the marketplace if you'd rather use one.

Do I need a paid Webflow plan?

For the embed, yes: Code Embed needs an active Site or Workspace plan. Webflow's help article on the custom form action doesn't list that requirement, but its integration page says most methods need a paid plan. A live business site will normally be on a Site plan anyway.

Does it work with Mailchimp's Free plan?

Yes, within the Free limits: 250 contacts and 500 sends a month since January 2026, and embedded forms must show the Referral badge. Check Mailchimp's pricing page for current numbers.

Can I add subscribers to a Mailchimp group from Webflow?

Yes, through the Mailchimp embed with a preselected hidden group, or through the API. The direct POST from a native Webflow form doesn't support groups.

Can I use Webflow Logic?

No. Webflow sunset Logic on June 27, 2025. Use Zapier or Make instead.

Can I use Mailchimp forms on Webflow CMS template pages with different tags?

Yes. The Flow Camp approach adds a plain text field such as Tag Values to the collection, then binds it to a hidden tags input in a Code Embed inside the form. Each CMS item sends its own tag. Test it on a test audience first, and use Zapier for tags if Mailchimp ignores the field.