Campaign Monitor

Webflow forms collect names and email addresses. They don't send newsletters or welcome and drip sequences. Submissions sit in your site's dashboard until someone exports them. Campaign Monitor handles the email side, and it needs a steady feed of subscribers from your site to do that work.

Connecting the two turns every submission into a subscriber the moment it lands. A signup form on a Webflow page can add contacts to a Campaign Monitor list and fire a welcome journey. It can also send a transactional confirmation. Orders from a Webflow ecommerce store can create or update subscriber records the same way.

Brand, performance, digital experience, and technical marketers get the most from this pairing, along with the agencies and freelance developers building for them. Marketing teams running content-heavy Webflow sites in retail, media and publishing, travel and hospitality, and nonprofits are Campaign Monitor's core segments.

How to integrate Campaign Monitor with Webflow

What is Campaign Monitor? Campaign Monitor is an email marketing platform that has operated for more than two decades and is now part of Marigold's product family, branded Campaign Monitor by Marigold. It includes a drag-and-drop email builder, hosted and embedded signup forms, automated journeys, transactional email, and list segmentation. Its REST API (v3.3) covers subscribers, lists, campaigns, journeys, transactional sends, and webhooks.

Teams pair the two platforms to grow a list from site traffic and act on it automatically. A gated resource page built on the Webflow CMS can trigger a targeted email series for each download. An event landing page can capture registrations and kick off confirmation and reminder sequences. There is no Campaign Monitor app in the Webflow Marketplace, so every path below runs through embeds or automation platforms. Direct API integration is also available.

The Campaign Monitor-Webflow integration supports three approaches:

• Signup form embeds and custom actions place Campaign Monitor forms on Webflow pages, or point native Webflow forms at Campaign Monitor, with no middleware.
• Zapier, Make, and viaSocket send Webflow form submissions and orders to Campaign Monitor lists without code.
• The Webflow and Campaign Monitor APIs give you full control over subscriber sync, journeys, and transactional email, but require server-side development.

You can combine two or more of these methods depending on the complexity of the setup.

Embed Campaign Monitor signup forms in Webflow

Campaign Monitor generates its own signup forms, and Webflow pages can host them directly. This path suits teams that want Campaign Monitor to process signups without an automation platform in between. Setup requirements differ across the hosted signup page, embedded form, and native Webflow custom-action options.

Link to a hosted signup page

A hosted signup page is a Campaign Monitor page with its own URL that needs no code and can add subscribers to one or more of your lists. The signup forms overview lists signup pages and landing pages as no-code options.

To use one on your site:

1. In Campaign Monitor, create a signup page or landing page for the list you want to feed.
2. In Webflow, set a button or link's destination to the generated URL.
3. Publish the site.

This works on any Webflow plan because no custom code is involved.

Paste an embedded form onto a Webflow page

Campaign Monitor's embedded form is the primary copy-paste method. You generate the HTML in Campaign Monitor and place it anywhere on a Webflow page with a Code Embed element. Custom fields from the subscriber list appear in the embedded form builder, and you can mark them required.

To set it up:

1. In Campaign Monitor, go to Signup forms > Embedded forms > Create an embedded form. Pick your list and styling, click Save, and copy the code.
2. In Webflow, open the Add panel and place a Code Embed element on the page.
3. Paste the snippet, click Save and close, and publish. For site-wide placement, follow Webflow's guide to custom code in head and body tags and paste the code into the footer code section instead.

The embedded form has these constraints:

• The form action and email field cannot be removed from the generated code. Neither can unique identifiers such as name="cm-f-jrddhr".
• Each subscriber list supports only one embedded form, and reCAPTCHA is built in by default.
• The embed requires JavaScript, so visitors with it disabled may see errors.
• Code Embed elements have a per-embed character limit and require a paid Site plan or a Core, Growth, Agency, or Freelancer Workspace.

Custom redirects after signup only work with embedded HTML forms, not hosted pages. Pick this method if you want a custom thank-you page under Lists & subscribers > Settings > Subscription success page.

Point a native Webflow form at Campaign Monitor with a custom action

Webflow forms support a custom action that posts submissions to an external URL. Webflow documents the pattern step by step for Mailchimp, and the same pattern transfers to Campaign Monitor's form endpoint, though no Campaign Monitor specific article exists. This keeps your form styled natively in Webflow instead of styling Campaign Monitor's markup.

To configure it:

1. Select the form, open the Settings panel, and click the add icon next to Send to.
2. Choose Custom action, enter Campaign Monitor's form action URL, and set the method to POST.
3. Match each field's name attribute to Campaign Monitor's unique identifiers, then click Save and publish.

Custom actions bypass Webflow's form processing entirely. Submissions aren't stored in your dashboard and no notification emails go out, per the forms overview, so use an automation platform if you need both.

Connect Webflow forms to Campaign Monitor with Zapier, Make, or viaSocket

Automation platforms are the most clearly documented no-code path that keeps Webflow form storage intact. Zapier publishes three prebuilt templates for this pair, all triggered by a new Webflow form submission. viaSocket publishes  prebuilt flows that pair its Webflow New Form Submission and New Order triggers with Campaign Monitor actions. Make lists verified apps for both platforms, with no prebuilt template. Its Webflow form modules pair with Campaign Monitor's Add a Subscriber module in a custom scenario. Before connecting to Zapier, your form needs at least one submission on record, per the Zapier integration doc.

The documented trigger-to-action pairs are:

• Webflow New Form Submission → Campaign Monitor Add Subscriber or Update Subscriber, with Find or Create Subscriber also available (Zapier)
• Webflow New Form Submission → Campaign Monitor Send Smart Transactional Email (Zapier)
• Webflow New Form Submission or New Order → Campaign Monitor Add Subscriber or Update a Subscriber, with Unsubscribe also available (viaSocket)
• Webflow form triggers → Campaign Monitor Add a Subscriber or Update a Subscriber, with Send a Smart Email also available (Make, custom scenario)

Zapier is the quickest to stand up because the templates already exist, and Make earns its extra setup when the scenario needs branching or field remapping before the subscriber call.

Build with the Webflow and Campaign Monitor APIs

Direct API integration gives you full control over field mapping and consent handling, including how errors are retried. It requires server-side development. Campaign Monitor authenticates with an API key over HTTP Basic auth (or OAuth 2.0, which it recommends), and that key can't live in client-side custom code. A middleware layer, such as a serverless function, receives Webflow webhooks and calls Campaign Monitor.

Campaign Monitor handles subscriber and email operations, while Webflow exposes site data and events through its API and webhooks:

• The Campaign Monitor API v3.3 handles subscribers, lists, transactional email, journeys, and campaign sends.
• The Webflow Data API v2 handles form submissions and CMS collection items.
• Webflow webhooks push form and CMS events to your endpoint. They also push ecommerce events.

Middleware ties the two sides together, receiving the Webflow event and making the Campaign Monitor call with the API key held server-side.

Sync form submissions with a form_submission webhook

The form_submission trigger is the only webhook type that supports a filter parameter, so you can target one form by name. Creating webhooks requires a site token or an OAuth bearer token from a Data Client App. Webhooks created with a site token after April 14, 2025 each get their own secret key for signature validation.

To implement the sync:

1. Register the webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks and include "triggerType": "form_submission", your middleware URL, and an optional filter such as { "name": "Newsletter Signup" }.
2. Verify each delivery. Compute an HMAC-SHA256 of timestamp + ":" + JSON.stringify(request_body) with your webhook secret and compare it to the x-webflow-signature header. Reject requests older than 5 minutes, per the webhooks guide.
3. Map payload.data to Campaign Monitor fields and call POST https://api.createsend.com/api/v3.3/subscribers/{listid}.json with EmailAddress, plus optional Name, CustomFields, Resubscribe, and ConsentToTrack, per the subscribers reference. A repeat email address is not an error: the existing subscriber's name, mobile number, and custom fields are overwritten with whatever you send, and anyone who previously unsubscribed stays off the list unless you set Resubscribe to true.

Failed deliveries retry automatically, so make your endpoint idempotent. For backfills, page through GET /v2/sites/{site_id}/form_submissions and batch records into Campaign Monitor's import endpoint, which accepts up to 1,000 subscribers per call.

Trigger transactional email and journeys from site events

The same middleware pattern powers confirmations and content-driven email. A form submission can send a Campaign Monitor smart email, and a published CMS item can fire a journey event.

To build either flow:

1. For confirmations, call POST https://api.createsend.com/api/v3.3/transactional/smartEmail/{smartEmailID}/send with To and Data. Include ConsentToTrack, per the transactional reference. Each send allows a maximum total of 25 recipients. That limit covers the To and CC fields as well as BCC.
2. Set AddRecipientsToList to true only when you have consent; it defaults to false.
3. For content triggers, register a collectionitempublished webhook, then call POST https://api.createsend.com/api/v3.3/events/publish/{clientId} with the required ContactID, such as { "Email": "subscriber@example.com" }. Include an EventName such as new_blog_post and the post data. Journey events are contact-specific, so middleware must safely select and iterate through eligible consenting contacts; for a newsletter broadcast, create and send a campaign instead. Event payloads max out at 32 KB, per the journeys reference.

The first send of a new EventName registers it in Campaign Monitor's journey-creation dropdown, so you can build the journey right after your first test event.

What you can build with the Campaign Monitor Webflow integration

Integrating Campaign Monitor with Webflow lets you capture and segment site visitors, then email them automatically without exporting form submissions or copying contacts by hand.

• Newsletter signup with welcome journeys: A blog page with a native form feeds readers into a Campaign Monitor list through Zapier, and a list-join trigger starts an automated welcome journey.
• Event registration pages: An event landing page captures registrations through native forms, and automation adds registrants to a list that sends confirmation and reminder emails. Post-event follow-up emails come afterward.
• Gated resource libraries: A multi-page library where downloading each asset triggers a targeted email series, and you can record which asset was downloaded with Campaign Monitor custom fields.
• Blog-to-newsletter pipelines: A collection_item_published webhook fires when a post goes live, and middleware either sends a contact-specific Campaign Monitor journey event for each eligible consenting subscriber or drafts a campaign announcing the post.

If you need more control over field mapping or consent handling, the API path also covers multi-list routing. For a worked example of the same Zapier trigger mapping, walk through Webflow forms to HubSpot. On the Webflow side, the Webflow MCP server lets an agent build and update the pages and Collections these lists feed from, with per-site agent instructions and permissions setting what it may change.