Webflow Make.com Integration

Leads sit in Webflow's Forms tab. Someone copies them into the CRM by hand on Friday afternoon. Or a scenario stopped weeks ago, and nobody noticed until sales asked where the demo requests went.

Make is a visual automation platform that connects Webflow to 3,000+ apps. That is Make's own figure on Webflow's integration page. You may still know it as Integromat, so if you searched for an Integromat Webflow setup, you are in the right place. One form submission can create a CRM contact, post to Slack and add a row to a sheet, without code.

Overflow builds your Webflow site and connects it to the rest of your stack with Make, so every form submission, CMS change and order lands where it should. A Webflow Make.com integration from us is part of the build, not an afterthought. We are an official Certified Webflow Partner. Book a call and we will map what your site needs to send, and where.

Why a Make scenario that works in testing still loses leads

Setting up a scenario is quick. Keeping it working is the job. Most lost leads come from small, ordinary changes that nobody connected to the automation:

• A renamed form. Someone tidies up form names in Webflow and the scenario keeps watching the old one.
• An unpublished CMS item. Make creates the item, but it never reaches the live site, because publishing is a separate step.
• A scenario nobody owns. The person who built it left, the connection expired, and the error emails go to an inbox no one reads.
• A webhook that went quiet. Webflow retries a failed webhook delivery up to 3 times at 10-minute intervals. After that, the webhook is switched off.

That is what we engineer for. The outcome you want:

• Route every lead to the right tool, complete and on time.
• Know when a scenario fails, and who fixes it.
• Change automations without waiting for a developer.

The old way: someone connects Make in an afternoon, tests one submission, and nobody owns it after that. The first sign of trouble is sales asking where the leads went.

The Overflow way: the scenario is part of the website build. Every trigger, field, destination and failure path is mapped, tested on the live site and documented for marketing.

Who this is for

B2B marketing leads and founders on Webflow, or moving to it, whose leads and content need to reach a CRM, an email tool, Slack, Google Sheets or Airtable. The trigger is usually a new site, a new CRM, a new market or a team that has outgrown copy-paste.

What can you automate with Webflow and Make?

Webflow handles design, content and hosting. It does not handle the follow-up after a form arrives or a CMS item changes. Webflow's own examples: form submissions creating CRM contacts, CMS changes pushing to email campaigns, and comments going to Slack or project tools. Make also has modules for ecommerce products, orders and inventory. We don't build ecommerce sites, so we leave those out here.

For a B2B site, three use cases matter most.

Route demo requests to the right people

A demo request creates a contact in your CRM, posts to a Slack channel and creates a task for the account owner. Make's Router and Filter modules branch the flow by event type or field value. A request from the enterprise form goes to one owner, a newsletter signup to another route. If the CRM is HubSpot or Salesforce, compare this with the native route on our Webflow HubSpot integration and Webflow Salesforce integration pages.

Create and update CMS items from other tools

Rows in a sheet, records in a base or pages in a workspace can become CMS items. Make has a template that creates CMS items from RSS feeds. See how this works with our Webflow Google Sheets integration, Webflow Airtable integration and Webflow Notion integration. The structure behind it is your Webflow CMS collections.

Send form signups to email tools

Make lists a template that routes Webflow form submissions to MailerLite subscribers. Our Webflow MailerLite integration page covers the details, and our Webflow Mailchimp integration page covers the alternative.

How does the Webflow Make.com integration work?

Make connects to Webflow through the Make app in the Webflow Marketplace, which uses OAuth 2.0. You can also connect through webhooks, or through the Webflow and Make APIs. Most setups start with the app and add the other routes as the logic grows. Older Integromat Webflow tutorials describe the same app under its former name.

The native app

The app has 40 modules: 2 triggers, 26 actions and 12 searches. They cover CMS collections and items, form submissions, products, orders, inventory, pages, assets, comment threads and site publishing.

1. In Make, open or create a scenario and add a Webflow module.
2. Click Create a connection, optionally name it, and save.
3. Log in to Webflow if prompted and confirm access.
4. Grant the "Forms data" scope if you plan to use form triggers.
5. Configure the module for your use case.

Watch Events and webhooks

The Watch Events trigger acts as a webhook listener. It receives the full payload, and Router or Filter modules branch the logic by event type. One scenario can handle several event types.

You can also set up webhooks yourself. Create a Custom webhook in Make, copy its URL, then paste it in Webflow under Site settings > Integrations > Webhooks and pick the event type. This gives you more control over which events reach Make.

The APIs

For bulk operations, custom endpoints or advanced data transformations, you use the Webflow API and Make's own API. That needs developer time. We scope it separately.

What you get when Overflow sets up your Make scenarios

You don't get a scenario someone clicked together. You get automations that are mapped, tested on the live site and documented, so your team knows where every submission goes.

Map every trigger before we build

For every form and CMS event, we write down what it represents (demo request, download, newsletter, event signup), which fields move, where they go and who follows up. It is the same rule we use for every Webflow integration: trigger, fields, permissions, transformations, destination, failure handling and owner, mapped before anything is installed.

Get the CMS publish chain right

Creating or updating a CMS item through Make does not make it visible on your live site. Item publishing and site publishing are separate steps. A typical chain is Create or Update Item, then Publish Item, then Publish Site.

We choose draft or live per workflow. When content needs checking first, we add a review step before anything is published. Note that CMS features need a Webflow CMS plan or higher.

Plan for what happens when a scenario fails

Without an error handler, a failing module stops the scenario. Whether the data is kept depends on your scenario settings. We attach error handling to every module that writes to a CRM or database, turn on storage of incomplete executions so failed submissions can be replayed after the fix, and add an alert to a channel people read. Every scenario gets a named owner.

Build forms and CMS fields that map cleanly

Clean automations start with clean fields. We use consistent field names across your Webflow forms and CMS collections, publish the form on the live domain and submit a test entry before we map anything. A renamed field later is a change we track, not a surprise.

Pass campaign data and respect consent

A lead without its source is half a lead. We carry UTM and source fields with each submission, so your CRM shows which campaign produced it. Consent and data protection are decisions made per form, together with you and your own advisers. We build what you decide. We don't give legal advice.

Hand it over to marketing

Handover includes live training, video tutorials and documentation. Your marketing team can read the scenarios, change them and fix them. We aim to create ownership, not dependency.

Make, Zapier or a native Webflow app: which connection fits?

• A native app fits a single destination. For HubSpot or Mailchimp, the Webflow HubSpot integration or Webflow Mailchimp integration is often simpler.
• Zapier fits simple trigger and action flows. See our Webflow Zapier integration page.
• Make fits when you need branching, routing and multi-step logic on a visual canvas, where you can see each step and data path at a glance.

Make is one more system, with its own plan, usage costs and owner. If a native app does the job, we use that instead. For sheet and base syncs, our Google Sheets and Airtable pages show the options. Browse all Webflow integrations to compare.

Moving to Webflow without breaking the automations you already run

On WordPress, form handlers and automations often live in plugins and theme code that nobody documented. Move the site and they stop working, quietly.

We inventory every form handler and automation first: what fires, what it sends and who relies on it. Then we rebuild them in Make, test them on the live Webflow site and switch DNS only when they work. Read more about our WordPress to Webflow migration approach.

How we deliver your Webflow Make integration

1. Audit and map. We list every form, CMS event, destination and owner.
2. Build forms and CMS. Consistent fields, clean collections, tracking fields in place.
3. Build and test scenarios on the live site. Real submissions, real destinations, failure paths included.
4. Document and train. Scenario documentation, video tutorials and a live session.
5. Handover. Your team owns the scenarios and knows who fixes what.

It can be part of a B2B Marketing Website build, our Playbook 01, where a typical project runs six to eight weeks. Or we add it to an existing Webflow site. See our Webflow agency page for how we work.

Proof from B2B teams we've built for

These are results of our Webflow work in general, not of Make automations specifically.

• Nedcargo: a WordPress to Webflow migration in 4 weeks.
• BlinkLab: 7 weeks from strategy to launch.
• Aumatics: 300%+ marketing ROI.

Who does the work

A small senior team. Jort Steinebach leads Webflow development, design systems and CMS architecture. He is a Certified Webflow Developer. Niels Voshol leads strategy and SEO. You talk to the people who build it.

What does a Webflow Make integration cost?

It depends on scope, so we quote after the audit, with cost and timing upfront. Five things drive it:

• The number of workflows.
• The number of destinations.
• CMS complexity, including review and publish steps.
• Error handling and alerting.
• Documentation and training.

Some costs sit with you, because you own the accounts: your Make plan, your Webflow plan (CMS features need a CMS plan or higher), and your CRM and email tools.

Webflow and Make FAQ

Does Webflow integrate with Make?

Yes. Make has a native app in the Webflow Marketplace with 40 modules. Webhooks and the APIs cover what the app doesn't.

Is Make the same as Integromat?

Yes. Integromat was renamed Make. Older tutorials and the Webflow app's callback address still use the Integromat name.

Why isn't my Webflow form triggering my scenario?

Check that the form is published on your live domain, that the "Forms data" scope is granted, and that the connection points at the right site. Then submit a fresh test entry.

Why don't my CMS items appear on the live site?

Creating or updating an item doesn't publish it. Add the Publish Item step and then the Publish Site step to your scenario.

Can Make delete or bulk update CMS items?

The native modules include delete and update for single items. Bulk or custom operations need the Webflow API and developer time.

Do you only set up scenarios or build the whole site?

Both. As a Certified Webflow Partner, we build B2B websites in Webflow and also add Make automations to existing sites.

Ready for automations your team can trust?

Every form mapped. Every failure has an owner. No funnies, no surprises. Book a call and we will look at what your Webflow site needs to send, and to which tools.

Using other tools? See all Webflow integrations.