Resources · Make integration

Webflow Make integrationAutomate Webflow with Make.

What if your Webflow CMS filled itself while you worked on the design? The Webflow Make integration gives you 40 modules, two of them triggers, covering items, products, orders, forms and assets. This guide shows marketers and site owners how to connect an account and build a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Webflow Make integration do for you?

The Webflow Make integration links your Webflow account to Make, a visual tool where you chain apps without writing code. Each chain is called a scenario (the automation you build), and each brick in it is a module. With Webflow, those bricks read, create and publish CMS items, products, orders and form submissions.

A blog that publishes from a spreadsheet or a writing tool. Your editors draft elsewhere, and Create an Item drops each article into the right collection. Publish an Item then pushes it live, so nobody copies and pastes into the Designer anymore.

An online store that keeps its back office tidy. List Orders pulls the orders of your site, Mark an Order Fulfilled/Unfulfilled/Refunded updates their status once shipping is done, and Update an Item Inventory corrects stock levels for a SKU.

A form inbox that stops living in Webflow. List Form Submissions reads what visitors sent through a form, and the next module can hand each entry to your CRM or your team chat.

What the modules do not cover can often be reached with Make an API Call, which talks to the Webflow API with the same connection. The Make documentation gives no numeric limit for this app, so test with small batches first.

Webflow also has a node on n8n: the Webflow n8n integration covers it, and n8n vs Make compares both tools. New to scenarios? Make training walks you through the editor.

Connect

How do you connect your Webflow account to Make?

  1. 01

    Add a Webflow module

    Open a scenario, add any Webflow module and click Create a Connection. A connection is your Webflow account linked to Make once; every Webflow module in every scenario can reuse it afterward.

  2. 02

    Name it and save

    Type a clear label in Connection name if you manage several sites or clients, then click Save. The name is optional, but it saves you from guessing later which account a scenario uses.

  3. 03

    Approve the access

    If Webflow asks you to log in, do it and confirm the access in the authorization window. Make then returns to the module, and the lists of sites and collections become available in its fields.

First scenario

Your first scenario: never lose a Webflow form request

GoalWhen the scenario runs on its schedule, Make lists the entries of your Webflow form and fills a hidden field on each one so your team sees it was picked up.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. No trigger here: the scenario starts on its schedule, set in the last step.

  2. 02

    Add List Form Submissions

    Search for Webflow, choose List Form Submissions and select your connection. Make lists what it can read, so you pick your site and form from a menu instead of typing an ID.

  3. 03

    Add Update a Form Submission

    Click the + on the right and add Update a Form Submission. Map the entry from the previous module, so each bundle (one item passed along, here one form entry) gets updated.

  4. 04

    Fill a hidden field

    In Update a Form Submission, write in one hidden field of the entry, for example the name of the person who follows up. That is what this module changes: the hidden fields.

  5. 05

    Test with Run once

    Send a test entry through your form, then click Run once. Open the bubble above each module to read the bundles it received and check the hidden field.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set the schedule (every 15 minutes by default, never below 15 on the Free plan), then flip the scenario on.

Triggers

What can start a Webflow scenario?

2 modules start a scenario when something happens in Webflow. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Webflow as soon as it happens.

Webflow1Watch Events

Watch Events

Instant trigger

In MakeTriggers when one of the selected events occurs.

This trigger wakes your scenario the moment one of the Webflow events you ticked in the module takes place. It is the entry point for reactions that should not wait, so the rest of the scenario acts on the change the second it lands.

How it fires
instant, Webflow calls Make through a webhook as soon as the event happens (the lightning badge on the module).
When to use it
pick it whenever the delay of a schedule would annoy a customer or a colleague.
Watch out
select only the events you really handle, otherwise every unrelated event still starts a run and counts operations.
Webflow2Watch Comment Threads

Watch Comment Threads

triggerIn the docs only

Watch Comment Threads looks for new discussion threads left on your Webflow site, the notes teammates or clients write while reviewing pages. Each new thread becomes one bundle for the rest of the scenario.

How it fires
scheduled, Make checks Webflow on the scenario's schedule (the clock badge), so a thread appears at the next check, not instantly.
When to use it
during a redesign, to route review feedback to the person in charge of each page.
Watch out
the Make documentation only lists this module, so test it with Run once on a real thread before relying on it.
Modules

What else can Make do in Webflow?

Webflow gives you 38 modules in 11 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Site

3 modules
Webflow1

List Sites

Search

In MakeLists of all sites the provided access token is able to access.

Returns every Webflow site your connection is allowed to reach, one bundle per site. Agencies juggling client projects get a clean inventory without clicking through the dashboard.

When to use it
at the start of a scenario that must loop over several sites, for example to publish all of them after a shared change.
Watch out
the result depends on what the account authorized, so a missing site usually means missing access.
Webflow2

Get a Site

Action

In MakeGet details of a specific site by ID.

Fetches the details of one site you identify by its ID. Think of it as a quick look at the site card before another module does something to it.

When to use it
when a later step needs information about the site itself, such as its name, to build a message or a report line.
Watch out
it reads one site only; to cover many, place List Sites before it instead of duplicating the module.
Webflow3

Publish a Site

Action

In MakePublishes an existing site.

Pushes the current version of an existing site live, the same result as hitting publish in Webflow. Your CMS changes made earlier in the scenario become visible to visitors.

When to use it
as the last module, after a batch of items was created or updated, so one publish covers them all.
Watch out
everything pending on the site goes live, including edits a colleague has not finished in the Designer.

Collection

2 modules
Webflow4

List Collections

Search

In MakeRetireves a list of collections

Gives you all the CMS collections of a site, like Blog Posts, Authors or Case Studies, each as its own bundle. It is the map you read before touching any item.

When to use it
in a scenario that must work across collections, or to discover which collection holds the content you want to sync.
Watch out
a search returns zero, one or many bundles, and each following module runs once per collection.
Webflow5

Get a Collection

Action

In MakeGets details of a collection.

Opens one collection and returns its details, so you see how it is built before sending data into it. Handy when a teammate renamed things and your mapping no longer matches.

When to use it
ahead of Create an Item, to check the collection structure your scenario writes into.
Watch out
it describes the container, not the entries; to read the articles or records inside, you need List Items.

Item

6 modules
Webflow6

List Items

Search

In MakeRetrieves a list of items for a collection.

Reads the entries stored in one collection, each blog post or team member becoming a bundle you can filter, count or copy elsewhere. It is the backbone of any export from the Webflow CMS.

When to use it
to mirror a collection into a spreadsheet, or to find entries that still need an update.
Watch out
a big collection means many bundles, and every module after it spends operations on each one.
Webflow7

Get an Item

Action

In MakeReturns the details of an item by ID.

Returns the full content of a single CMS entry when you already know its ID. Unlike a list, it goes straight to the record you care about.

When to use it
after a trigger or another app hands you an item ID and you need its current content before editing it.
Watch out
without a valid ID the module fails, so map the ID from a previous module rather than typing it by hand.
Webflow8

Create an Item

Action

In MakeCreates a new item for a collection.

Adds a new entry to a collection: a blog article, a job offer, a directory listing. Content written in another tool lands in Webflow without anyone retyping it.

When to use it
when a new row, form or record elsewhere should become a page on your site.
Watch out
creating is not publishing; add Publish an Item or Publish a Site afterward if visitors must see the entry.
Webflow9

Update an Item

Action

In MakeUpdates an existing item for a collection.

Changes an existing CMS entry, for instance a price, a date or an event status, without opening the Designer. The rest of the item stays as it was.

When to use it
when the source of truth lives in another app and the site must follow each change made there.
Watch out
you need the item ID; pair it with List Items or Get an Item to find the right entry first.
Webflow10

Publish an Item

Action

In MakePublishes an existing collection item.

Puts one collection entry live on its own, without republishing the whole site. That is the gentle option when only a single article is ready.

When to use it
right after Create an Item or Update an Item, once the entry has passed its review.
Watch out
run it only on items you have checked, since the change is public as soon as the module succeeds.
Webflow11

Delete an Item

Action

In MakeDeletes an existing item for a collection.

Removes an entry from a collection for good. Expired offers, sold-out events or duplicate records disappear from the CMS without manual cleanup.

When to use it
when an item is marked as closed or archived in the app that manages it.
Watch out
a deletion cannot be undone from Make, so place a filter before this module and test on a dummy entry first.

Product

5 modules
Webflow12

List Products

Search

In MakeRetrieves a list of products.

Fetches the products of a Webflow Ecommerce store, one bundle per product. It is the starting point for catalogue exports, price checks or feeds for other sales channels.

When to use it
to copy your catalogue into a spreadsheet or compare it with your supplier data.
Watch out
a catalogue with lots of products multiplies the operations of every module that follows.
Webflow13

Get a Product

Action

In MakeGets detail of an existing product.

Reads the full record of one product you already point to. Where List Products sweeps the store, this module zooms on a single reference.

When to use it
when an order or a message names a product and you need its current details before replying or updating it.
Watch out
map the product ID from a previous module; a typed value breaks as soon as the product changes.
Webflow14

Create a Product

Action

In MakeCreates a new product item.

Adds a new product to your Webflow store from data prepared elsewhere, such as a supplier sheet or a product database. New references reach the shop without manual entry.

When to use it
when a product is approved in your internal catalogue and should appear online.
Watch out
check for an existing product with List Products first, or reruns will create duplicates.
Webflow15

Update a Product

Action

In MakeUpdates an existing product.

Edits an existing product, for example its name or description, while leaving the rest of the listing intact. Your shop stays in sync with the tool where the team writes product copy.

When to use it
after a product sheet is revised in another app.
Watch out
variants and their prices are handled by Update a Product SKU, not by this module.
Webflow16

Update a Product SKU

Action

In MakeUpdates an existing product SKU.

Targets one SKU, the specific variant of a product such as a size or a color, and changes it without touching the parent product. That precision matters when only one variant moves.

When to use it
when a supplier changes the price or data of a single variant.
Watch out
stock levels have their own module, Update an Item Inventory, so do not look for quantities here.

Order

4 modules
Webflow17

List Orders

Search

In MakeRetrieves a list of orders created for a given site.

Collects the orders placed on a given site, each order arriving as a bundle. Your sales can then flow to accounting, a shipping tool or a simple team recap.

When to use it
to sweep orders that still need handling, or to rebuild a history in a spreadsheet.
Watch out
add a filter on status so already processed orders are not handled a second time.
Webflow18

Get an Order

Action

In MakeGets details of an existing order.

Pulls every detail of one existing order: what was bought and by whom. Customer service gets the full picture without logging into Webflow.

When to use it
when a support ticket or an email mentions an order and you want to attach its details automatically.
Watch out
it needs the order ID, which usually comes from List Orders or from the event trigger.
Webflow19

Update an Order

Action

In MakeUpdates an order.

Modifies an existing order record, so the data in Webflow matches what happened downstream in your logistics or support tools.

When to use it
when another system holds information that should be written back onto the order.
Watch out
to change the fulfillment status itself, use Mark an Order Fulfilled/Unfulfilled/Refunded, which exists for that exact job.
Webflow20

Mark an Order Fulfilled/Unfulfilled/Refunded

Action

In MakeMark an order status as fulfilled, unfulfilled or refunded.

Switches an order to fulfilled, unfulfilled or refunded in one step. The order status in Webflow finally reflects the parcel that left the warehouse or the refund your team granted.

When to use it
when your shipping tool confirms a delivery or your payment tool records a refund.
Watch out
a refund status can change what the customer sees, so double check the filter that leads to it.

Inventory

2 modules
Webflow21

Get an Item Inventory

Action

In MakeGets the current inventory levels for a particular SKU item.

Tells you how many units of a given SKU are in stock right now. A quick read that keeps your alerts and dashboards honest.

When to use it
before promising availability to a customer, or to warn the buyer when a variant runs low.
Watch out
the value is the one at the time of the run; stock can move again before the next module acts on it.
Webflow22

Update an Item Inventory

Action

In MakeUpdates the current inventory levels for a particualr SKU item.

Sets the stock level of a SKU in Webflow from the figure your warehouse or point of sale holds. No more selling a variant that ran out in the physical shop.

When to use it
whenever another system records a stock movement for that variant.
Watch out
if two tools write stock to Webflow, pick one as the reference to avoid values that overwrite each other.

Asset

5 modules
Webflow23

Create an Asset Folder

Action

In MakeCreates an asset folder within a given site.

Creates a folder in the asset library of a site, the place where images and files are stored. Media stay organized per campaign or per client from day one.

When to use it
when a new project or collection starts and its visuals need a home.
Watch out
look up existing folders with List Asset Folders first, otherwise each run adds a twin folder.
Webflow24

Get an Asset Folder

Action

In MakeGets details about a specific asset folder.

Reads the details of one specific asset folder, useful to confirm it exists and to pass its information to the next steps.

When to use it
when a scenario stores a folder reference and must check it before working with the assets inside.
Watch out
it gives the folder, not the files; List Assets is the module that returns the images themselves.
Webflow25

List Assets

Search

In MakeRetrieves a list of assets for a specified site.

Returns the assets of a site, the images and files uploaded to its library, as separate bundles. It is the way to audit a media library that grew without rules.

When to use it
to build an inventory of visuals, or to find files a cleanup scenario should remove.
Watch out
sites with heavy libraries return many bundles, so filter early to save operations.
Webflow26

List Asset Folders

Search

In MakeLists asset folders within a given site.

Shows all asset folders of a site in one go. Before creating or sorting anything, you see how the library is already organized.

When to use it
ahead of Create an Asset Folder, to reuse a folder that already exists with the same name.
Watch out
each folder is its own bundle, so a following module runs once per folder unless you filter.
Webflow27

Delete an Asset

Action

In MakeDeletes an existing asset.

Removes one file from the asset library. Outdated visuals and leftovers from old campaigns go away without a manual sweep.

When to use it
at the end of a cleanup scenario that listed assets and filtered the ones nobody needs.
Watch out
a deleted file may still be used on a page; check before removing it, because Make cannot bring it back.

Form

5 modules
Webflow28

List Forms

Search

In MakeRetrieves a list of forms for a given site.

Lists the forms that live on a site, from the contact form to the newsletter signup. You get their references without inspecting each page.

When to use it
as a first step when you want to process the entries of several forms in the same scenario.
Watch out
the module returns forms, not what visitors typed; for that, chain List Form Submissions.
Webflow29

List Form Submissions

Search

In MakeRetrieves a list of form submissions for a given form.

Pulls what visitors sent through one form, each entry becoming a bundle ready for your CRM, your inbox or a sheet. Leads stop waiting inside Webflow.

When to use it
to route contact requests to sales, or to back up entries outside the site.
Watch out
the same entries come back on each run, so keep track of the ones already sent to avoid duplicates.
Webflow30

Get a Form

Action

In MakeReturns information about a given form.

Returns information about a single form, handy to know which form an entry came from when several sit on the same site.

When to use it
when you tag leads by source and need the form details to label them correctly.
Watch out
it describes the form only; to read an actual entry, use Get a Form Submission.
Webflow31

Get a Form Submission

Action

In MakeReturns information about a given form submission.

Reads one entry sent through a form, with everything the visitor filled in. It is the precise tool once you know which submission matters.

When to use it
after a trigger or a list gives you a submission, to fetch its full content before sending it on.
Watch out
map the submission ID from an earlier module; a hand-typed value only ever matches one entry.
Webflow32

Update a Form Submission

Action

In MakeUpdates hidden fields on a form submission.

Writes values into the hidden fields of an existing submission. Your team can stamp an entry as handled, or add a reference from your CRM, right inside Webflow.

When to use it
after a lead has been processed elsewhere and you want the trace to live on the submission.
Watch out
only hidden fields can be changed; what the visitor typed stays as it was sent.

Page

2 modules
Webflow33

Get a Page

Action

In MakeReturns metadata information for a single page.

Returns the metadata of one page, the information search engines and social networks read, such as its title. SEO checks no longer require opening every page setting.

When to use it
to audit a key landing page, or to copy its metadata into a review sheet.
Watch out
the module name says Get a Page, but it reads metadata, not the visible content of the page.
Webflow34

List Pages

Search

In MakeRetrieves a list of pages for a given site.

Returns every page of a site as a list of bundles. Paired with Get a Page, it becomes a small SEO audit running across the whole site.

When to use it
after a redesign, to check that no page was left without its metadata.
Watch out
CMS item pages are content of their collection; read those through List Items.

Comment

3 modules
Webflow35

Search Comments Threads

SearchIn the docs only

Looks through the comment threads of your site and returns the ones that match, one bundle per thread. Scattered review notes turn into a list you can work through.

When to use it
to gather open feedback before a launch, instead of waiting for new threads.
Watch out
the Make documentation only names this module, so run it once on your site to see what it really returns.
Webflow36

Get a Comment Thread

ActionIn the docs only

Opens one comment thread and brings back its content, so the right person reads the remark without hunting for it on the canvas.

When to use it
right after Watch Comment Threads or Search Comments Threads, to enrich each thread before notifying someone.
Watch out
the documentation gives no detail on this module; confirm the output with Run once before mapping it further.
Webflow37

List Comment Thread Replies

SearchIn the docs only

Collects the replies posted under a thread, each reply as a bundle. The whole conversation around a design note becomes readable outside Webflow.

When to use it
when a summary for a client or a project lead must include the back and forth, not only the first comment.
Watch out
a long discussion produces many bundles; add an aggregator if you want one single message.

Other

1 module
Webflow38

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Sends a request of your choice to the Webflow API, using the connection you already set up. It is the escape hatch for anything the other Webflow modules leave out.

When to use it
when the Webflow API documentation lists an endpoint that no module above covers.
Watch out
you write the request yourself, so read the Webflow API documentation and test the call with Run once.
Need help

Need help automating Webflow with Make?

A person reads every message.

FAQ

Webflow and Make: your questions

01Is the Webflow Make integration free to use?
Yes, Webflow is a standard app in Make, so it works on the Free plan too. The Free plan still has limits worth knowing: two active scenarios, a minimum of 15 minutes between scheduled runs, five minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to one minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle. Your Webflow site plan is a separate matter, handled on the Webflow side.
02What does it take to connect Webflow to Make?
A Webflow account and a Make account, nothing more according to the documentation. Add any Webflow module, click Create a Connection, give it a name if you like and save. Webflow may then ask you to log in and confirm access. If your company uses its own Webflow app, open Show Advanced Settings and paste its client credentials. The connection is created once and shared by every Webflow module, so you will not repeat this step for each scenario.
03Does the Webflow trigger react in real time?
It depends on which trigger you pick. Watch Events is instant: Webflow calls Make through a webhook the moment one of the selected events happens, so the scenario starts right away. Watch Comment Threads is scheduled: Make checks Webflow on the scenario schedule, every 15 minutes by default, and never faster than every 15 minutes on the Free plan. On a paid plan, the scheduled one can check as often as every minute. Choose the instant trigger when a delay matters to a customer.
04What if the Webflow module you need is missing?
Use Make an API Call. This module sends any request to the Webflow API with the connection you already have, so an endpoint missing from the 40 modules is still within reach. You write the request yourself, which means reading the Webflow API documentation first. The Make documentation lists no numeric limit for Webflow, so there is no published cap to plan around; still, test on a small batch with Run once before sending hundreds of items through a scenario.
05Make or n8n for Webflow: which one fits?
Both can do the job, so the choice rests on your context. Webflow has a node on n8n as well as 40 modules in Make, including Make an API Call for anything unlisted. If your other automations already run in Make, keep Webflow there and reuse the same connection logic. If your team works in n8n daily, stay with it. On Make, the Free plan allows two active scenarios, which is enough to test a real Webflow workflow before deciding. The dedicated comparison page on this site details both tools.