MailerLite

Your Webflow site handles design, CMS, and hosting, but email marketing isn't built in. To grow an audience, you'll need an external tool to capture signups, trigger welcome sequences, and segment contacts.

Connecting MailerLite fills that gap. Form submissions flow into subscriber groups, automations deliver welcome emails and lead magnets, and pop-ups or event-driven syncs work without leaving the platform. It's useful for freelancers, SaaS marketers, ecommerce stores, and newsletter creators alike.

How to integrate MailerLite with Webflow

What is MailerLite? MailerLite is an email marketing platform with campaign builders, signup forms, pop-ups, landing pages, and automation workflows. It offers subscriber segmentation through groups and custom fields, and ships with a REST API for programmatic subscriber management. Small businesses, creators, and nonprofits use it most often.

You'll want to connect MailerLite with Webflow when email signups need to work automatically. A blog might capture newsletter subscribers from sidebar forms. An ecommerce store might route order data into post-purchase email sequences. Pick the integration method based on how much design control you want and whether you'd rather avoid third-party automation subscriptions.

You can connect MailerLite and Webflow in 3 ways:

• Embedded MailerLite forms and pop-ups capture subscribers directly on your pages — no third-party automation tool required.
• Zapier and Make route form submissions and order events to MailerLite while keeping your custom form styling.
• The Webflow and MailerLite APIs let you manage subscriber creation, group assignment, and bidirectional data sync directly, though they require server-side development.

Most setups combine two or more of these methods depending on the complexity you need.

Embed MailerLite forms and pop-ups with Code Embed elements

MailerLite connects to your site through embedded form or pop-up code. This approach works on all MailerLite plans and needs no third-party automation subscription. MailerLite's embedded form builder generates HTML and JavaScript that you paste into your page using a Code Embed element. Embedded forms render with MailerLite's styling rather than your own design system.

Add an inline embedded form

Inline forms sit directly within a page layout — a blog sidebar, footer section, or hero area. MailerLite handles double opt-in, group assignment, and GDPR consent checkboxes inside the embedded form itself.

To add an embedded form:

1. In MailerLite, go to Forms and click the Embedded forms tab, then Create form.
2. Name the form, select a subscriber group, and customize the fields, button text, and design using the sidebar Design and Settings tabs.
3. Click Next and copy the embed code from the Overview section.
4. In your project, add a Code Embed element to the page where the form should appear.
5. Paste the MailerLite embed code into the Code Embed element and publish your site.

Embedded forms include these capabilities out of the box:

• Built-in double opt-in handling without custom code
• Automatic group assignment configured in MailerLite
• Pop-up forms with exit-intent and scroll triggers
• GDPR-compliant consent checkboxes managed by MailerLite

These defaults make embedded forms the fastest setup path when design matching isn't your top priority.

You need a paid site plan for the Code Embed element to render on published sites. On the free Starter plan, custom code doesn't execute on published pages.

Add site-wide pop-ups with a tracking script

Pop-up forms with exit-intent and scroll triggers need MailerLite's universal JavaScript snippet placed in your site's head code. This approach displays pop-ups across every page automatically, instead of requiring individual Code Embed elements.

To add site-wide pop-ups:

1. In MailerLite, go to Forms and create a pop-up form with your preferred trigger (exit-intent, scroll percentage, or time delay).
2. Copy MailerLite's universal tracking snippet from the form's installation instructions.
3. In your project, go to Site settings and open the custom code in head and body tags section.
4. Paste the snippet into the Head code field and save.
5. Publish your site.

MailerLite includes several pop-up types: floating, slidebox, and full-screen. Promotion pop-ups with countdown timers are available on MailerLite's Advanced plan only. Cookie-blocking browser extensions can interfere with MailerLite's pop-up display logic. MailerLite uses cookies to track whether a visitor has already seen a form, and cookie duration can vary by setup.

Connect MailerLite and Webflow with Zapier or Make

Reach for automation platforms when you want to keep your form styling and still sync data to MailerLite. Zapier offers direct Webflow-to-MailerLite connections, and Make support is verified for MailerLite Classic. This approach preserves your form styling, custom success states, and validation behavior. Submission data routes to MailerLite in the background.

Route form submissions with Zapier

Zapier offers pre-built templates connecting Webflow triggers to MailerLite actions. No code required. Eight templates cover common workflows including subscriber creation from form submissions and group assignment from order events.

To set up a Zapier connection:

1. Go to zapier.com/apps/mailerlite/integrations/webflow and click Try it on a template matching your use case.
2. Select Webflow as the trigger app, choose the Webflow New Form Submission trigger event, and connect your Webflow account.
3. Select MailerLite as the action app and choose the MailerLite Create Subscriber or MailerLite Add Subscriber to Group action. Connect your MailerLite account.
4. Map your form fields (email, name) to the corresponding MailerLite subscriber fields, including any custom fields like company or industry.
5. Test the Zap and turn it on.

This setup keeps your form styling intact while MailerLite handles subscriber management behind the scenes.

Zapier includes these Webflow triggers for MailerLite workflows:

• Webflow New Form Submission — for routing contact and signup form data
• Webflow New Collection Item — for triggering emails when CMS content is published
• Webflow Order Submitted — for post-purchase subscriber group assignment
• Webflow Order Updated — for syncing order status changes to subscriber records

These triggers cover the most common lead capture and ecommerce automation use cases.

Zapier's polling frequency and task limits vary by plan. For MailerLite accounts created after March 2022, use the "MailerLite" connector on Zapier. Accounts created before March 2022 need the separate MailerLite Classic connector.

Build Webflow form scenarios with Make (MailerLite Classic)

Make gives you more control over data transformations and conditional routing than Zapier does. It has 40 Webflow modules and 26 MailerLite Classic modules, plus pre-built scenario templates for subscriber syncing.

These steps apply to MailerLite Classic.

To connect Webflow and MailerLite Classic through Make:

1. In Make, create a new scenario and add the Webflow module as a trigger.
2. Click Create a Connection, connect your Webflow account, and grant the Forms data scope.
3. Select the Webflow Watch Form Submissions trigger event. Choose your target site and form.
4. Add a MailerLite Classic module and select the MailerLite Classic Create or Update Subscriber action.
5. Map your form fields to MailerLite subscriber fields, turn on the scenario, and test with a form submission.

You can also use webhooks to send form data into Make in real time. Go to Site settings > Integrations > Webhooks, paste a Make webhook URL, and select form submissions as the event. This path eliminates polling delays and delivers data instantly.

Make's MailerLite connector is labeled "MailerLite Classic." Make's Webflow modules use API v2. If you have older scenarios still running on pre–March 31, 2025 Webflow v1 connections, audit and update them.

Build with the Webflow and MailerLite APIs

For direct control over subscriber management, conditional group assignment, and bidirectional data sync, connect the Webflow and MailerLite APIs through a server-side application. This approach skips third-party automation subscriptions. It also handles real-time webhook-driven workflows that no-code tools can't replicate. But you'll need to write and host server-side code.

Three APIs come into play here:

• The MailerLite API handles subscriber creation, group management, custom field updates, and webhook registration
• The Data API handles CMS collections and form submissions
• Webhooks trigger real-time events between systems when forms are submitted or orders are placed

These endpoints give you direct control over how subscriber data moves between the two platforms.

Both APIs use Bearer token authentication and return JSON responses. Never place MailerLite API keys in client-side custom code — page source is visible to anyone who inspects it. Route all authenticated MailerLite API calls through an external serverless function or backend server.

Sync form submissions to MailerLite subscribers

A common pattern registers a webhook for form submissions, then upserts each submission as a MailerLite subscriber. Your server receives form data in real time and creates or updates the subscriber record with group assignment and custom field mapping.

To implement this:

1. Register a webhook by sending a POST request to https://api.webflow.com/v2/sites/:site_id/webhooks with triggerType set to form_submission and url pointing to your server endpoint.
2. Parse the incoming webhook payload on your server. The payload.data object contains the form field values, including email and any custom fields.
3. Create or update the subscriber in MailerLite by sending a POST request to https://connect.mailerlite.com/api/subscribers with the subscriber's email, fields, and group IDs.

Here's what a Node.js implementation of the webhook handler looks like:

const express = require('express');
const app = express();
app.use(express.json());

app.post('/webhooks/webflow-form', async (req, res) => {
  const { payload } = req.body;
  if (!payload?.data?.email) {
    return res.status(400).json({ error: 'No email in payload' });
  }

  const { email, name } = payload.data;

  const response = await fetch('https://connect.mailerlite.com/api/subscribers', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'Accept': 'application/json',
      'Authorization': `Bearer ${process.env.MAILERLITE_API_TOKEN}`
    },
    body: JSON.stringify({
      email,
      fields: { name },
      groups: [process.env.MAILERLITE_GROUP_ID],
      status: 'active'
    })
  });

  if (response.status === 422) {
    const err = await response.json();
    console.error('Validation error:', err.errors);
    return res.status(422).json(err);
  }

  const data = await response.json();
  res.status(200).json({ success: true, subscriberId: data.data.id });
});

The POST /api/subscribers endpoint is an upsert. If the email already exists, MailerLite updates the record. Groups passed in a POST request are additive only, so existing group memberships stay intact.

Assign groups conditionally based on form data

When forms capture more than just an email address, you can route subscribers to different MailerLite groups based on their responses. A form with a "product interest" dropdown, for example, can send enterprise leads to one group and small business leads to another.

To implement conditional group assignment:

1. Cache your MailerLite groups at server startup by calling GET https://connect.mailerlite.com/api/groups and storing the id to name mapping.
2. Write a resolver function that inspects incoming form fields and returns the appropriate group IDs.
3. Pass the resolved group IDs array in the groups field of your POST /api/subscribers request.

function resolveGroups(formData) {
  const groups = [];
  if (formData.newsletter === 'yes') {
    groups.push(process.env.GROUP_NEWSLETTER);
  }
  if (formData.product_interest === 'enterprise') {
    groups.push(process.env.GROUP_ENTERPRISE);
  }
  return groups;
}

If you later need to update a subscriber with PUT /api/subscribers/{id}, keep in mind that the groups array in a PUT request is destructive — the subscriber is removed from any groups not listed in the array. That's different from the POST endpoint, where groups are only added.

Write MailerLite subscriber data back to Webflow CMS

MailerLite webhooks can trigger CMS item creation. This comes in handy for populating collections like "Featured Members" or "Testimonials" when specific subscriber events happen.

To implement this:

1. Register a MailerLite webhook by sending a POST request to https://connect.mailerlite.com/api/webhooks with the subscriber.created event and your server's endpoint URL.
2. When your server receives the event, create a CMS item by sending a POST request to https://api.webflow.com/v2/collections/:collection_id/items with the subscriber's data mapped to your collection fields.
3. Publish the CMS item with a separate POST request to https://api.webflow.com/v2/collections/:collection_id/items/publish, passing the item ID in the itemIds array. Creating a CMS item doesn't automatically make it visible on the live site.

This pattern turns subscriber events into publishable content automatically.

MailerLite webhook endpoints must respond within 3 seconds, or the delivery counts as failed. If your handler performs database writes or additional API calls, process them asynchronously and return a 200 response right away. MailerLite retries failed deliveries three times (at 10 seconds, 100 seconds, and 1,000 seconds after the initial failure), and deactivates the webhook after 3 days of consecutive errors.

What you can build with the MailerLite Webflow integration

Connecting MailerLite to your site lets you capture, segment, and nurture email subscribers directly — no manual data transfers between platforms.

• Newsletter signup with automated welcome sequences: Place embedded forms or native Webflow forms across blog sidebars, homepage hero sections, and resource pages. Each form can route to a different MailerLite group, and tailored welcome email sequences trigger based on where the visitor signed up. A photography portfolio, for instance, could have separate signup paths for wedding inquiries and portrait session interest.
• Lead magnet delivery funnels: Build a landing page with a form offering a free download. Connect it to a MailerLite automation that delivers the file link instantly via email. The automation can continue with a nurture sequence that introduces your services over the following days. MailerLite's lead magnet tutorial walks through the automation configuration.
• Post-purchase email flows for Webflow ecommerce: Route order events to MailerLite subscriber groups through Zapier, then trigger post-purchase automations that send thank-you emails, request product reviews, or recommend related items. Group assignment based on product category lets you send targeted follow-ups instead of generic messages.
• Event registration with timed reminder sequences: Create a registration form for a webinar or workshop and sync submissions to a MailerLite group. Configure a time-based automation that sends a confirmation email, a pre-event reminder, and a post-event replay link on a set schedule.

If you need more control over conditional subscriber routing or bidirectional CMS sync, go with the API integration path.