Menu

Mattering Automations Webflow integration

Connect Webflow to Mattering Automations: sites, publishing, CMS items with an explicit staged-vs-live model, page SEO metadata, forms, assets, webhooks, and ecommerce reads as workflow steps, authenticated with a Webflow site token.

The Mattering Automations Webflow integration adds Webflow to your automation canvas: list sites and custom domains, create, update, and publish CMS collection items with an explicit staged-vs-live model, rewrite page SEO metadata, read and update localized page content, read forms and form submissions, list assets with their CDN URLs, manage webhooks, and read ecommerce products and orders.

Setup takes a few minutes: generate a site token in Webflow's site settings, attach it as a credential in Mattering, and test the connection. This guide walks through each step and ends with the full node reference.

The publishing model is staged-first by construction. Webflow: Create Collection Item (Staged) and Webflow: Update Collection Item (Staged) touch only the design-time layer; nothing reaches visitors until Webflow: Publish Collection Items promotes the exact item ids you choose. The nodes that change the live site immediately say so in their names, and Webflow: Publish Site pushes all staged changes, design and content alike, with no API rollback. Keep the publish steps behind a condition, an approval task, or a manual run, and verify the integration with read nodes only.

Before you start

  • A Webflow account with a site. Webflow's free Starter plan includes API access and site tokens, which covers reads and staged CMS writes on a test site.
  • Site admin access, since site tokens are created from the site's settings by an admin. On Enterprise plans, a workspace token covers every site in the workspace and works identically here.
  • A Mattering workspace with access to the Automations app.
  • For the ecommerce nodes: a site with Webflow Ecommerce enabled, since the product and order endpoints only exist on ecommerce sites.

Create a Webflow site token

Mattering authenticates to Webflow with a site token, sent as a Bearer credential on every request. A site token is scoped to one site, and the permission areas it grants are chosen at creation; automating several sites means one connector credential per site, or an Enterprise workspace token, which behaves the same here because every node takes explicit site and collection ids.

In Webflow, open Site Settings and go to Apps & Integrations.
In the API access section, generate a site token and grant the permission areas your automations need: read and write on Sites, CMS, Pages, Forms, Assets, and Ecommerce covers the full node set.
Copy the token. Up to 5 site tokens can exist per site.
Webflow site tokens expire after 365 days of inactivity; any API call resets the clock, and a token can also be revoked manually from the same settings page. Permission areas are fixed at creation, so a token missing an area cannot be edited into shape: create a new token and update the credential instead.

Connect Webflow to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Webflow from the list.
Click Create new credential, paste your site token, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection: Mattering lists the sites the token can reach and confirms it authenticates.
Click Connect. All 37 Webflow nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: a Webflow section should list the query and action nodes. Drop Webflow: List Sites onto the canvas and run a test step. It takes no parameters and is a safe, read-only call; a site token returns exactly its one site, and a workspace token returns every site in the workspace. Note the site id, because almost every other node needs it.

To confirm the CMS surface, run Webflow: List Collections with that site id, then Webflow: Get Collection (Schema) on one collection: it returns every field's slug, type, and required flag, which is exactly what item writes are keyed by. Everything in the verify path is read-only; nothing here can publish or change the live site.

Node reference

37 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 24

Webflow: Get Asset

webflow_get_asset

Fetch one asset's metadata: CDN URL, content type, size, alt text and responsive variants.

Webflow: Get Collection (Schema)

webflow_get_collection

Fetch a collection's full definition including its field schema: every field's slug, type (PlainText, RichText, Image, Reference, Option, Number, DateTime and so on), required flag and validations. Read this before building fieldData for create/update item nodes: the field slugs here are the keys fieldData takes.

Webflow: Get Collection Item (Staged)

webflow_get_item

Fetch one STAGED item with its full fieldData, draft/archived flags and publish timestamps. lastPublished older than lastUpdated means the staged copy has unpublished edits.

Webflow: Get Form Schema

webflow_get_form_schema

Fetch one form's definition: its fields (display name, type, placeholder), response settings and placement. Useful for mapping submission payload keys before wiring a submissions automation.

Webflow: Get Form Submission

webflow_get_form_submission

Fetch one form submission by id, with the submitted values under formResponse keyed by field name.

Webflow: Get Live Item

webflow_get_live_item

Fetch one LIVE item: the currently published fieldData as visitors see it. 404 if the item exists but is not published.

Webflow: Get Order

webflow_get_order

Fetch one order in full: line items, amounts, customer and shipping details, fulfillment and dispute state.

Webflow: Get Page Content

webflow_get_page_content

Read a static page's content nodes: text nodes (with html and plain text), images (alt + assetId) and component instances, each with a node id. This is the read half of page-content localization, and a useful content audit read on its own. Paged with limit/offset (max 100 nodes per call).

Webflow: Get Page Metadata

webflow_get_page_metadata

Fetch one page's settings: title, slug, SEO title and description, Open Graph fields, draft/archived state and published path.

Webflow: Get Product

webflow_get_product

Fetch one product with its full field data, variant properties and all of its SKUs (each with price and variant values).

Webflow: Get Site

webflow_get_site

Fetch one site: display name, custom domains (with the domain ids that Publish Site needs), locale configuration (including each locale's cmsLocaleId for the CMS item nodes), and the last published/updated timestamps.

Webflow: List Assets

webflow_list_assets

List a site's uploaded assets with ids, CDN URLs (hostedUrl), content types, sizes, alt text and responsive variants. The asset id is what CMS image fields reference. Upload is not available through this connector (Webflow asset upload is a multipart S3 handshake). Webflow rate limit: 60 requests per minute on Starter/Basic site plans (120 on CMS/Ecommerce/Business), shared across all nodes.

Webflow: List Collection Items (Staged)

webflow_list_items

List a collection's STAGED items (the design-time layer, including drafts and unpublished edits) with full fieldData. Filter by exact name or slug, sort, and page with offset/limit (max 100). Webflow rate limit: 60 requests per minute on Starter/Basic site plans (120 on CMS/Ecommerce/Business), shared across all nodes.

Webflow: List Collections

webflow_list_collections

List a site's CMS collections with ids, names and slugs. The collection id returned here is what every item node needs; use Get Collection for the field schema.

Webflow: List Custom Domains

webflow_list_custom_domains

List the custom domains connected to a site, with each domain's id and last-published date. The domain ids returned here are what the Publish Site node's customDomains field takes.

Webflow: List Form Submissions

webflow_list_form_submissions

List submissions for one form, each with the submitted values under formResponse keyed by the form's field names. Note submissions contain whatever visitors typed (often personal data), and node outputs are stored in automation execution records. Webflow rate limit: 60 requests per minute on Starter/Basic site plans (120 on CMS/Ecommerce/Business), shared across all nodes.

Webflow: List Form Submissions by Site

webflow_list_site_form_submissions

List ALL form submissions across a site, optionally filtered to one core form by its elementId (the formElementId from List Forms). The elementId filter is the right way to catch every submission of a form that lives inside a component, where each component instance otherwise yields a separate form id. Webflow rate limit: 60 requests per minute on Starter/Basic site plans (120 on CMS/Ecommerce/Business), shared across all nodes.

Webflow: List Forms

webflow_list_forms

List a site's forms with ids, field definitions, the page each form lives on, and response settings. The form id feeds List Form Submissions; the formElementId feeds the site-level submissions filter. Webflow rate limit: 60 requests per minute on Starter/Basic site plans (120 on CMS/Ecommerce/Business), shared across all nodes.

Webflow: List Live Items

webflow_list_live_items

List a collection's LIVE items: only what is currently published on the site, with the published fieldData (staged edits and drafts are excluded; use List Collection Items for those). Same filters, sorting and offset/limit paging as the staged list. Webflow rate limit: 60 requests per minute on Starter/Basic site plans (120 on CMS/Ecommerce/Business), shared across all nodes.

Webflow: List Orders

webflow_list_orders

List an ecommerce site's orders with customer info, purchased items, totals and Stripe payment details. Filter by status. Order data includes customer names, emails and addresses, and node outputs are stored in automation execution records. Webflow rate limit: 60 requests per minute on Starter/Basic site plans (120 on CMS/Ecommerce/Business), shared across all nodes.

Webflow: List Pages

webflow_list_pages

List a site's static and template pages with ids, titles, slugs, SEO/Open Graph settings and draft/archived flags. Pages linked to a CMS collection carry that collectionId. Webflow rate limit: 60 requests per minute on Starter/Basic site plans (120 on CMS/Ecommerce/Business), shared across all nodes.

Webflow: List Products

webflow_list_products

List an ecommerce site's products, each with all of its SKUs (variants with prices). Pagination counts products only, not SKUs. Requires the site to have ecommerce enabled. Webflow rate limit: 60 requests per minute on Starter/Basic site plans (120 on CMS/Ecommerce/Business), shared across all nodes.

Webflow: List Sites

webflow_list_sites

List the sites this token can access, with ids, names, custom domains, locales and publish timestamps. A site token returns exactly its one site; a workspace token returns every site in the workspace. Takes no parameters, so it doubles as the credential health check for the connector. Webflow rate limit: 60 requests per minute on Starter/Basic site plans (120 on CMS/Ecommerce/Business), shared across all nodes.

Webflow: List Webhooks

webflow_list_webhooks

List the webhooks registered on a site via the API, with trigger types, target URLs and last-triggered timestamps. Webhooks created by hand in the Webflow dashboard may not appear here (Webflow documents this list as App-created registrations).

Action nodes 13

Webflow: Create Collection Item (Staged)

webflow_create_item

Create a STAGED item in a collection. This touches only the STAGED layer: nothing changes on the public site until the item is published (Publish Items or Publish Site). fieldData is keyed by the collection's field slugs (name and slug are required; see Get Collection for the rest). Follow with Publish Items to push it live. To create several items in one call, put {"items": [...]} in the free-form body field instead of using fieldData. Returns 202 Accepted.

Webflow: Create Live Item (Publishes Immediately)

webflow_create_live_item

CHANGES THE LIVE SITE IMMEDIATELY: create an item that is published to the live site in the same call, skipping the staged-then-publish step (the site must have been published at least once). Real visitors see it as soon as the call returns. Prefer Create Collection Item plus Publish Items when a review step matters. Multiple items: put {"items": [...]} in the free-form body field. Returns 202 Accepted.

Webflow: Create Webhook

webflow_create_webhook

Register a webhook so Webflow POSTs event payloads to a URL of your choice: form submissions, site publishes, page and collection item lifecycle events, ecommerce orders and inventory changes, new comments. Management only: this node registers the webhook; receiving the calls is the target URL's job. Limit of 75 registrations per trigger type per site. Webhooks created with a site token get their own secret for signature validation. Note: Webflow's reference page marks this endpoint for OAuth app tokens while its webhooks guide documents site-token creation; if a site token gets a 403 here, create the webhook in the Webflow dashboard instead.

Webflow: Delete Collection Item

webflow_delete_item

DESTRUCTIVE: permanently delete a collection item (the staged record and its content); there is no undo via the API. If the item is currently published, its live page stops resolving after the next publish. To merely take an item off the live site while keeping it, use Unpublish Live Item instead. Returns 204 with an empty body.

Webflow: Delete Form Submission

webflow_delete_form_submission

DESTRUCTIVE: permanently delete a form submission and its data; there is no undo. Useful for spam cleanup and data-removal requests. Returns 204 with an empty body.

Webflow: Delete Webhook

webflow_delete_webhook

Remove a webhook registration: Webflow stops sending that event to the target URL immediately. Reversible by re-creating the webhook, though a re-created site-token webhook gets a NEW signing secret, so signature validation on the receiving end must be updated. Returns 204 with an empty body.

Webflow: Publish Collection Items

webflow_publish_items

PUBLISHES CONTENT LIVE: promote staged items to the live site by id, making them visible to real visitors immediately (the site itself must have been published at least once). This is the second half of the safe staged workflow: create or update staged items, then publish exactly the ids you mean. Returns 202 with publishedItemIds plus per-item errors for ids that could not be published (draft items, for example, are skipped).

Webflow: Publish Site

webflow_publish_site

PUBLISHES THE LIVE SITE: pushes ALL staged changes (design and content) to the selected domains, changing what real visitors see immediately, and there is no API rollback. At least one of customDomains or publishToWebflowSubdomain must be set. Set pageId to publish a single page instead of the whole site (publishing staged pages to production still publishes all staged changes). Webflow allows ONE successful site publish per minute. Returns 202 Accepted; publishing completes asynchronously (watch the site_publish webhook event or poll Get Site lastPublished).

Webflow: Unpublish Live Item

webflow_unpublish_live_item

Take an item OFF the live site without deleting it: the live copy is removed immediately (its page stops resolving) and the staged copy remains with isDraft set true, so re-publishing restores it. This is the reversible take-down; Delete Collection Item is the permanent one. Returns 204 with an empty body.

Webflow: Update Collection Item (Staged)

webflow_update_item

Update a STAGED item: send only the fieldData keys to change (a partial patch). This touches only the STAGED layer: nothing changes on the public site until the item is published (Publish Items or Publish Site). Changing the slug breaks existing links to the old slug when published.

Webflow: Update Live Item (Publishes Immediately)

webflow_update_live_item

CHANGES THE LIVE SITE IMMEDIATELY: patch a published item's fields and the updates go straight to what visitors see, no publish step. Send only the fieldData keys to change. Prefer Update Collection Item plus Publish Items when a review step matters.

Webflow: Update Page Content (Secondary Locales)

webflow_update_page_content

Update text and component content on a static page IN A SECONDARY LOCALE (up to 1000 nodes per request). Webflow documents this endpoint for localization only: localeId is REQUIRED and must be a secondary locale id; the default locale's static content cannot be edited via the API. Workflow: Get Page Content to find node ids and current html, then send the changed nodes here. Keep any data-w-id attributes from the original html so links and custom attributes stay consistent across locales.

Webflow: Update Page Metadata

webflow_update_page_metadata

Update a page's settings: title, slug, SEO title/description and Open Graph fields. This is the workhorse for SEO automation (rewrite meta titles and descriptions at scale). Changes are staged; they reach the live site on the next publish. Slug changes are ignored on the home page, collection template pages and utility pages, and a changed slug changes the page URL when published.

Using the integration

On the automation canvas

Webflow nodes chain with every other node: records in a Mattering database can become staged CMS items through Webflow: Create Collection Item (Staged), a review task in Mattering Productivity can gate Webflow: Publish Collection Items, and a scheduled Webflow: List Form Submissions sweep can turn what visitors submitted into tasks and records.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can list pages with their SEO settings, read collection schemas, and compare staged items against live ones through the same nodes your workflows use. The read nodes and staged writes are the safest Webflow surface to hand an agent; keep the publish nodes behind human gates.

The staged-vs-live model

CMS items exist in two layers with separate nodes for each. Staged writes (Webflow: Create Collection Item (Staged) and Webflow: Update Collection Item (Staged)) change only the design-time copy, and Webflow: Publish Collection Items promotes chosen ids live. Webflow: Create Live Item (Publishes Immediately) and Webflow: Update Live Item (Publishes Immediately) skip staging and change the public site in the same call. Webflow: Unpublish Live Item is the reversible take-down: the live copy disappears while the staged copy survives as a draft. Webflow: Delete Collection Item is the permanent one, with no undo via the API. Webflow: Publish Site pushes all staged changes at once, design and content alike, with no API rollback and one successful publish allowed per minute.

Read the collection schema before writing items

Webflow: Get Collection (Schema) is the schema endpoint: it returns every field's slug, type, and required flag, and item writes key their fieldData by exactly those slugs, with name and slug required at create. Reading it first is what turns guessed field names into correct ones, which matters most when an agent is doing the writing.

SEO metadata and localized page content

Webflow: Update Page Metadata is the SEO workhorse: it rewrites a page's title, slug, SEO title and description, and Open Graph fields, and the changes are staged until the next publish, so bulk rewrites stay reviewable. Webflow: Update Page Content (Secondary Locales) writes text and component content into secondary locales only; Webflow documents that endpoint strictly for localization, and the default locale's static content cannot be edited via the API. Webflow: Get Page Content is the read half and works as a content audit on any locale.

Webhook management, not an inbound trigger

Webflow: Create Webhook, Webflow: List Webhooks, and Webflow: Delete Webhook manage a site's webhook registrations, up to 75 per trigger type; receiving the calls is the target URL's job, so there is no inbound Webflow trigger in this integration. Point registrations at a URL you operate, or poll with the scheduled list nodes instead. Deleting and re-creating a webhook mints a new signing secret, so update signature validation on the receiving end.

Troubleshooting

Test Connection fails with a 401
The token is invalid, revoked, expired, or picked up stray whitespace when pasted. Webflow site tokens expire after 365 days of inactivity, so a long-idle integration can lapse on its own. Generate a new site token in Site Settings > Apps & Integrations and update the credential on the connector.
Test Connection passes but a node returns a 403
The token is missing the permission area that node needs. The connection test only lists sites, so a token without CMS, Pages, Forms, Assets, or Ecommerce permissions passes it while those nodes are refused. Permission areas are fixed at creation: create a new token with the right areas and update the credential.
I created or updated an item but the live site did not change
That is the design working. Webflow: Create Collection Item (Staged) and Webflow: Update Collection Item (Staged) touch only the staged layer. Run Webflow: Publish Collection Items with the item ids to push them live, and note that it skips items still marked as drafts, reporting them in its per-item errors.
A node returns a 429
The credential hit Webflow's rate limit: 60 requests per minute on Starter and Basic site plans, 120 on CMS, Ecommerce, and Business plans, shared across all nodes. Webflow sends a Retry-After header, typically 60 seconds. Separately, Webflow allows only one successful site publish per minute, so space out Webflow: Publish Site steps.
Webflow: Create Webhook returns a 403 with a site token
Webflow's docs disagree with themselves on this endpoint: the API reference marks it for OAuth app tokens while the webhooks guide documents site-token creation. The node is built per the guide, which is the newer document. If your site token is refused, create the webhook by hand in the Webflow dashboard; be aware that Webflow: List Webhooks may not show dashboard-created webhooks, since Webflow documents that list as app-created registrations.
Webflow: Get Live Item returns a 404 for an item I can see in the designer
The item exists but is not published: live reads only see the published layer. Fetch it with Webflow: Get Collection Item (Staged) instead, and compare its lastPublished and lastUpdated timestamps to see whether staged edits are waiting. Publish it with Webflow: Publish Collection Items if it should be live.
Webflow: Update Page Content (Secondary Locales) is rejected
This endpoint works on secondary locales only: localeId is required and must be a secondary locale id, because Webflow documents the endpoint for localization and the default locale's static content cannot be edited via the API. Get the locale ids from Webflow: Get Site, and keep the data-w-id attributes from the original html when rewriting nodes so links and custom attributes stay consistent across locales.
Webflow: List Products or Webflow: List Orders fails on my site
The ecommerce endpoints only exist on sites with Webflow Ecommerce enabled; on other sites they fail rather than return empty lists. The integration ships ecommerce reads only, so there is nothing to configure on the Mattering side: enable ecommerce on the Webflow site or leave these nodes out of the workflow.

Webflow is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products