Make

The Make Webflow integration (formerly Integromat) connects your Webflow site to 2,000+ apps through a visual scenario builder with around 40 native Webflow modules spanning CMS collections, forms, ecommerce, site management, and comments. It is the power-user automation tool for teams that need branching logic, routers, iterators, and high-volume runs at a lower per-operation cost than Zapier. If your workflow needs conditional routing, array iteration, or reactions to almost any object inside Webflow, Make is the stronger choice.

What you can do with Make

Make extends Webflow by treating site events as triggers and chaining them into multi-step scenarios on a drag-and-drop canvas. Here are the practical things the Make Webflow integration lets you build.

• Sync CMS items bidirectionally — Watch for new or updated collection items, then create or update matching records in Airtable, Notion, Google Sheets, or HubSpot, and push changes back to Webflow.
• Automate form routing — When a form is submitted, split submissions by type using routers: support questions go to Intercom, leads to HubSpot, and newsletter signups to Mailchimp, each with its own mapped fields.
• Run ecommerce back-office — Fire on new orders or abandoned carts to update inventory in Stripe, generate invoices in QuickBooks, and notify fulfillment in Slack, all in one scenario.
• Bulk-manage CMS content — Iterate over hundreds of items, transform fields, replace text, and publish or unpublish in batches that would be tedious or impossible manually.
• React to site changes — Trigger scenarios on site publish, domain changes, or collection item updates, then log events, alert the team, or sync to analytics.
• Schedule precisely — Run scenarios down to one-minute intervals on paid plans, far finer than most alternatives, for near real-time sync.

How Make's Webflow modules work

Make's Webflow app provides roughly 40 modules split across triggers, actions, and searches. The CMS group is the deepest: Watch Collection Items, Create an Item, Update an Item, List Items, Get an Item, Delete an Item, and Publish/Unpublish an Item. The forms group fires on new form submissions and lets you search submissions by field. The ecommerce group covers products, orders, and abandoned carts. Site management modules react to site publish and other site-level events, and comment modules cover new and updated comments on CMS pages.

All of these live on Make's visual scenario canvas, where you drag modules onto a grid and connect them into a chain. The canvas is where Make's power becomes obvious: you can insert Routers to split a scenario into parallel branches, Filters to let data through only when conditions match, Iterators to loop over arrays one element at a time, and Error Handlers to define what happens when a module fails. Each module that executes during a run consumes credits, and the entire scenario runs on a schedule you control.

Because the Webflow integration runs on Webflow API v2, connections use OAuth 2.0 with scopes rather than legacy API tokens. You authorize once inside Make, grant the specific scopes your scenario needs (for example, read and write CMS items), and the connection persists across modules in that scenario.

How to set up Make with Webflow

1. Create a Make account at make.com and log in, then click Create a new scenario from the dashboard.
2. Add a Webflow trigger module — Click the plus icon, search for Webflow, and add a trigger such as Watch Form Submissions, Watch Collection Items, or Watch Orders depending on what should start your scenario.
3. Authorize the connection — Make opens an OAuth 2.0 window; sign in to Webflow, select the site, and grant the scopes the module needs. Repeat this for any additional Webflow sites you connect.
4. Verify your CMS plan — If your scenario uses any CMS module, confirm your Webflow site has a CMS plan enabled, since CMS modules fail without it. Forms, ecommerce, and site-management modules work on any plan.
5. Configure the trigger — Pick the specific collection, form, or order source, set filters or limits, and run the module once to pull sample data you will map in later steps.
6. Chain your action modules — Add destination apps (HubSpot, Airtable, Slack, Google Sheets), then map fields from the trigger output into each action module's inputs.
7. Add routing logic — Insert Routers, Filters, or Iterators where the workflow needs branching, conditional execution, or looping over arrays.
8. Schedule and turn on — Set the schedule interval (down to one minute on paid plans), run the scenario once to test end-to-end, then toggle it to ON.

Make pricing

Make uses credit-metered pricing: every module execution in a scenario consumes credits, and plans bundle a monthly credit allowance plus limits on active scenarios and scheduling interval. The Free plan is genuinely usable for testing; paid plans unlock unlimited scenarios and one-minute scheduling.

Make vs. Zapier for Webflow

Make and Zapier overlap on the basics — both connect Webflow to thousands of apps and handle forms, CMS, and ecommerce events — but they differ sharply on depth, control, and cost. Make offers a deeper native Webflow module set and a true visual programming canvas; Zapier offers faster setup and a larger app catalog. Choose based on workflow complexity and volume.

Best Make + Webflow workflows

Bidirectional CMS sync with Airtable

Keep a marketing Airtable base and your Webflow CMS in lockstep. When an editor updates a record in Airtable, a Make scenario updates the matching Webflow item; when an item changes in Webflow, the change syncs back. This turns Airtable into a structured editorial backend for non-technical content teams.

Smart form routing to HubSpot and Slack

Route every Webflow form submission by type using a Router. Demo requests create a HubSpot deal and notify sales in Slack, support questions open an Intercom ticket, and newsletter signups add a contact to Mailchimp — all from one trigger module.

Abandoned cart and order automation

Fire on new Webflow orders or abandoned carts to update Stripe, generate a QuickBooks invoice, decrement inventory, and message the fulfillment team. One scenario replaces several disconnected tools and keeps ecommerce data consistent across systems.

Scheduled content publishing

Build a scenario that reads a backlog of draft CMS items, applies filters (for example, only items tagged ready), publishes them on a staggered schedule, and logs each publish event to a Google Sheet. This gives content teams a queue-driven publishing workflow without manual clicks in the Designer.

Site publish alerts and audit logging

Trigger on Webflow site publish or domain changes to post an alert in Slack, append a timestamped row to an audit Google Sheet, and ping a monitoring endpoint. You get a complete change log and instant team awareness every time the live site updates.

Limitations to know

• Steeper learning curve — Make's routers, iterators, and error handlers are powerful but require more setup time than Zapier's guided editor, so expect a longer ramp for non-technical users.
• Credit-metering surprises — Every module execution costs credits, and a single scenario with loops and branches can burn through an allowance faster than expected; monitor usage before scaling.
• CMS plan required for CMS modules — Any module that touches CMS collections needs a Webflow CMS plan enabled on the site, so non-CMS sites cannot use Watch or Create Collection Item modules.
• Free plan caps — The Free plan limits you to two active scenarios and a 15-minute minimum interval, which rules out near real-time automation without upgrading.

Related Webflow integrations

• Zapier — the simpler, broader-catalog alternative for trigger-to-action Webflow automation.
• Airtable — the most popular structured backend for bidirectional CMS sync via Make.
• HubSpot — a common destination for form submissions and ecommerce order data.
• Blog: 20 Best Webflow Integrations — the full ranked list for 2026.
• Guide: Connect a Webflow form to Zapier or Make — step-by-step form automation setup.