Resources · n8n integration

Webflow n8n integrationAutomate Webflow with n8n.

Webflow holds the content, n8n handles the part that repeats. The Webflow n8n integration exposes 5 operations on collection items, plus a trigger that listens to 8 events, from a form submission to a new order. Written for people who still update collections by hand.

Try the Webflow integration on n8nSee the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What can the Webflow n8n integration actually do?

The Webflow node talks to the Webflow API from inside a workflow. One resource, Item, and 5 operations on it: create, get, get many, update, delete. Next to it sits the Webflow Trigger, which registers a webhook, a URL that Webflow calls the moment something happens on the site, and starts a workflow on any of 8 events.

First scenario, a lead list that fills itself. The trigger fires on form_submission, the contact goes straight into Mailchimp, and a copy lands in Google Sheets for whoever follows up. Nobody exports a CSV on Monday morning.

Second, a blog that publishes itself. An article approved elsewhere becomes a collection entry through item.create, with Live switched on so it reaches the published site immediately. The correction that always arrives two hours later goes through item.update without anyone opening the editor.

Third, a shop that reacts. ecomm_new_order starts the run, the order is announced in Slack, and the confirmation leaves through Gmail. Stock gets the same treatment with ecomm_inventory_changed.

Now the limits, because they matter before you design anything. The node covers collection items and stops there. Anything else you might want to reach in Webflow is simply not an operation on this node. When that happens, the HTTP Request node calls any endpoint of the API and reuses the same credential through predefined authentication, so there is no second setup to maintain.

Two details worth knowing up front. The trigger watches one site, chosen in Site Name or ID, and listens to one event, so a project spanning several sites or several events means several workflows. And the Webflow Data API V1 is deprecated: on OAuth2, the Legacy toggle exists for that case and stays off otherwise. If this is your first build in n8n, the n8n training and the n8n review cover the ground around the node itself.

Connect

How do you connect Webflow to n8n?

  1. 01

    Generate the access token in Webflow

    Two authentication methods are supported: API access token and OAuth2. The token is the quickest route. Open your site's Site Settings > Apps & integrations > API access and select Generate API token. A site has to exist before you can do this, since access tokens are site-specific and there is nothing to attach the token to otherwise.

  2. 02

    Store the credential once in n8n

    In n8n, open the Credentials menu and create a Webflow credential, then paste the Access Token. A credential is saved once and reused by every workflow that needs it. For OAuth2, register an application in your Webflow workspace, copy the OAuth callback URL from n8n into it as a Redirect URI, then paste back the Client ID and the Client Secret.

  3. 03

    Pick a site and run one read

    Drop a Webflow node on the canvas, select the credential, then choose Site Name or ID and Collection Name or ID from the dropdowns n8n fills for you. Run item.getAll once against a small collection. If entries come back, the credential reaches what you need. On the trigger side the same check means picking the site and one event, then activating the workflow.

Triggers

What starts a Webflow workflow?

Webflow Trigger is the node that starts a workflow when something happens in Webflow. It listens to 8 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Webflow account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

collection_item_changed.*1
  • collection_item_changed.
    • collection_item_changed
collection_item_created.*1
  • collection_item_created.
    • collection_item_created
collection_item_deleted.*1
  • collection_item_deleted.
    • collection_item_deleted
ecomm_inventory_changed.*1
  • ecomm_inventory_changed.
    • ecomm_inventory_changed
ecomm_new_order.*1
  • ecomm_new_order.
    • ecomm_new_order
ecomm_order_changed.*1
  • ecomm_order_changed.
    • ecomm_order_changed
form_submission.*1
  • form_submission.
    • form_submission
site_publish.*1
  • site_publish.
    • site_publish

Configuration notes

01Set up the Webflow TriggerThe Webflow Trigger is the node that starts a workflow when something happens in Webflow, instead of you pressing Execute. Version 2 works over a webhook: activating the workflow registers the n8n URL with Webflow, and each matching event arrives within seconds. Nothing to schedule, no interval to tune.

The Webflow Trigger is the node that starts a workflow when something happens in Webflow, instead of you pressing Execute. Version 2 works over a webhook: activating the workflow registers the n8n URL with Webflow, and each matching event arrives within seconds. Nothing to schedule, no interval to tune.

Key parameters

  • Site Name or ID: the site being watched, chosen from the list n8n loads with your credential, or written as an expression such as {{ $json.siteId }} when the value comes from an earlier node. An expression is n8n's way of reading a field off the incoming item.
  • Event: the one event this trigger reacts to, picked among 8. There is no wildcard option, so a workflow never listens to everything at once.
When to use it
whenever Webflow is the starting point of the process rather than its destination, and waiting for a scheduled run would be too late.
02Collection item eventsThree of the 8 events follow the life of a collection entry: collection_item_created, collection_item_changed and collection_item_deleted. Each one hands the workflow the entry that moved, so a mirror of the collection can stay current without reading the whole collection back every time.

Three of the 8 events follow the life of a collection entry: collection_item_created, collection_item_changed and collection_item_deleted. Each one hands the workflow the entry that moved, so a mirror of the collection can stay current without reading the whole collection back every time.

Key parameters

  • Event: choose the direction that matters, creation for a new entry, update for a correction, deletion for a cleanup. Covering all three means three workflows.
  • Site Name or ID: the events are scoped to the site, not to a single collection, so entries from every collection on that site come through.
Use cases
a new case study is added and the workflow posts it to the team channel with its link; a deleted entry clears the matching row in the tracking sheet so the two stay aligned.
03Ecommerce eventsThe shop side contributes three more: ecomm_new_order when an order is placed, ecomm_order_changed when that order is modified afterwards, and ecomm_inventory_changed when stock moves. Together they let a workflow follow a sale end to end without anyone watching the Webflow dashboard.

The shop side contributes three more: ecomm_new_order when an order is placed, ecomm_order_changed when that order is modified afterwards, and ecomm_inventory_changed when stock moves. Together they let a workflow follow a sale end to end without anyone watching the Webflow dashboard.

Key parameters

  • Event: one per workflow. An order pipeline that cares about both the sale and its later changes runs as two separate workflows feeding the same downstream steps.
  • Site Name or ID: the site running the shop. These events only exist where ecommerce is set up, so the trigger stays quiet on a plain content site.
Use cases
a new order opens a fulfillment task and posts the details to the warehouse channel; an inventory change below your comfort level sends a restock reminder to the buyer.
04Form submission and site publishform_submission delivers the fields of a Webflow form the moment a visitor sends it. site_publish fires when the site is published. They have little in common beyond being the two events that are not about collection entries, and both make solid entry points for a workflow.

form_submission delivers the fields of a Webflow form the moment a visitor sends it. site_publish fires when the site is published. They have little in common beyond being the two events that are not about collection entries, and both make solid entry points for a workflow.

Key parameters

  • Event: form_submission for anything lead related, site_publish for release work and post-publish checks.
  • Site Name or ID: forms from every page of that site arrive through the same trigger, so routing by form name happens downstream in the workflow, not in the node.
Use cases
a contact form feeds the mailing list and the sales channel in one run, with no form tool in between; a publish event starts a link check and lets the client know the new version is online.
Actions

What can the Webflow node do?

The Webflow node exposes 5 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateDelete
Item✓✓✓✓✓

Item

5 operations
01

Create an item

item.create

What you see in n8n

Notes & use cases

Adds an entry to a collection and returns it as Webflow stored it, identifier included, which the following nodes reuse.

Key parameters

  • Site Name or ID: the site holding the target collection, picked from the list or given as an expression.
  • Collection Name or ID: the collection receiving the entry.
  • Live: on, the entry is published on the live site right away; off, it waits in the collection until the next publish.
  • Fields: the content itself, added one by one with Add Field, usually fed by expressions such as {{ $json.title }} from the node before.
Use cases
an approved draft becomes a published article without anyone retyping it in the editor.
02

Delete an item

item.deleteItem

What you see in n8n

Notes & use cases

Removes one entry from a collection for good. Webflow works from the identifier here, never from the name you read in the editor, so the workflow has to carry that value.

Key parameters

  • Site Name or ID: the site whose collection holds the entry.
  • Collection Name or ID: the collection to operate on.
  • Item ID: the entry to remove, typically passed along as {{ $json.itemId }} from the step that identified it.
Use cases
a job listing that expired in the applicant tracking tool disappears from the careers collection the same day.
03

Get an item

item.get

What you see in n8n

Notes & use cases

Reads one entry and returns its fields, without changing anything. Useful as the step that decides what the rest of the workflow does.

Key parameters

  • Site Name or ID: the site containing the collection.
  • Collection Name or ID: where the entry lives.
  • Item ID: the entry to read, often taken from a trigger event with an expression.
Use cases
before pushing an update, the workflow reads the current values and skips the write when nothing changed, which keeps the site history readable.
04

Get many items

item.getAll

What you see in n8n

Notes & use cases

Lists what a collection holds, one n8n item per entry. Filter, compare or count them downstream.

Key parameters

  • Site Name or ID: the site to read from.
  • Collection Name or ID: the collection to list.
  • Return All: on, n8n walks through the API pages and brings back every entry; off, it stops at Limit.
  • Limit: the maximum number of entries returned when Return All is off, handy while testing on a large collection.
Use cases
a nightly export of the whole product collection into a sheet, to spot the entries missing an image.
05

Update an item

item.update

What you see in n8n

Notes & use cases

Rewrites the fields of an existing entry and keeps the same identifier, so links and references pointing at it survive.

Key parameters

  • Site Name or ID: the site holding the collection.
  • Collection Name or ID: the collection the entry belongs to.
  • Item ID: the entry to modify.
  • Live: on, the new values appear on the published site; off, they stay in the collection.
  • Fields: only the fields you add here are sent, so a price refresh touches the price alone.
Use cases
stock and price synced from the back office every morning.
Need help

Need help automating Webflow with n8n?

A person reads every message.

FAQ

Webflow and n8n, the usual questions

01Is the Webflow n8n integration free?
Yes on the n8n side. The Webflow node and the Webflow Trigger ship with n8n, so there is nothing to install and nothing extra to pay to use them. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance installed with Docker or npm under the Community Edition and its Sustainable Use licence. A workflow behaves the same way in both places, so you can prototype on one and run it on the other. What a Webflow plan costs is a separate question and depends on your own account.
02Which credentials do you need for Webflow in n8n?
Two methods work, and the node itself has no authentication selector: you pick the method when you create the credential. The first is an API access token, generated from Site Settings, Apps and integrations, API access, with Generate API token. It requires an existing site, and it only covers that site. The second is OAuth2: register an application in your Webflow workspace, add the OAuth callback URL from n8n as a Redirect URI, then bring the Client ID and the Client Secret back into n8n. If you are still on the deprecated Webflow Data API V1, the Legacy toggle handles it. Either credential serves both the node and the trigger.
03What are the limits of the Webflow node?
It depends what you expect from it. The node exposes one resource, Item, with 5 operations, so anything outside collection entries is not covered and no amount of configuration will add it. The answer in that case is the HTTP Request node, which calls any endpoint of the Webflow API and reuses the same credential through predefined authentication. On reads, Get Many stops at Limit unless Return All is enabled, which is the classic reason an export looks incomplete. And on writes, Live decides whether the change reaches the published site or waits in the collection.
04Does the Webflow trigger react in real time?
Yes. The Webflow Trigger works over a webhook, which means Webflow calls an n8n URL as soon as the event happens rather than n8n asking repeatedly whether something changed. n8n registers that URL with Webflow when you activate the workflow, and events arrive within seconds. There is no polling interval to set and no delay to account for in your design. Two constraints to plan around: the trigger watches a single site, set in Site Name or ID, and listens to a single event among the 8 available, with no wildcard. Several events means several workflows.
05n8n or Make to automate Webflow?
It depends on what you need to control. Make is a hosted automation platform, billed per operation, with no self-hosting option. n8n runs either on its own cloud or on your own server, which matters when the form submissions and order data passing through the workflow should stay on infrastructure you own. The cost model differs too: per operation on one side, per instance or per plan on the other. On the Webflow side the coverage is what this page describes, 5 operations and 8 trigger events, so compare that against your actual list of use cases rather than against a feature count.
Same platform

Other docs you might need on this stack.

Browse all integrations