Menu
Mattering Automations connector

A Webflow MCP that respects the line between staged and live

Connect one site token and Webflow sites, CMS collections, pages, forms, assets, webhooks, and ecommerce orders become workflow steps for visual automations and AI agents. Staged CMS writes change nothing on the public site; the nodes that touch the live site say so in their names.

37 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Webflow MCP connector does

The Webflow connector for Mattering Automations is 37 nodes across the Data API v2: sites and custom domains, site publishing, CMS collections with their full field schemas, collection items in both the staged and live layers, page metadata and localized page content, forms and form submissions, assets with their CDN URLs, webhook management, and ecommerce product and order reads.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer which pages are missing SEO descriptions, which staged items carry unpublished edits, and what a form collected this week, without anyone opening the Webflow designer.

Because Mattering is a work platform rather than middleware, website work lands somewhere useful by default: records in a Mattering database can become staged CMS items with a review task attached, form submissions can open tasks in Mattering Productivity, and a page SEO audit can write its findings back into a database the team already works in.

The staged-vs-live split is structural, not advisory. Creating or updating a staged item touches only the design-time layer and changes nothing visitors see; Webflow: Publish Collection Items promotes exactly the item ids you choose. The live-item write nodes are named for what they do, Webflow: Create Live Item (Publishes Immediately) and Webflow: Update Live Item (Publishes Immediately), and Webflow: Publish Site pushes all staged changes, design and content alike, with no API rollback and a limit of one successful publish per minute. Put the publish steps behind a condition, an approval task, or a manual run.

One connection, three surfaces

  • Visual automations. Drag Webflow nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Webflow node, ready to drop on the canvas

37 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 24

Webflow: Get Asset

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

Webflow: Get Collection (Schema)

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)

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

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

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

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

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

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

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

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

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

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)

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

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

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

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

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

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

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

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

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

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

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

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)

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)

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

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

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

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

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

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

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

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)

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)

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)

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

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.

Connecting Webflow takes one credential

Webflow issues site tokens from Site Settings > Apps & Integrations > API access; a site admin creates them and chooses the permission areas the token grants at creation. A site token is scoped to one site (automating several sites means one credential per site, or an Enterprise workspace token), up to 5 tokens can exist per site, and a token expires after 365 days of inactivity, with any API call resetting the clock. The token is sent as a Bearer credential on every request.

1

In Webflow, open Site Settings > Apps & Integrations > API access and generate a site token, granting the permission areas your automations need: Sites, CMS, Pages, Forms, Assets, and Ecommerce cover the full node set.

2

In Mattering Automations, open Connectors, click Add Connector, choose Webflow, and create a credential with that token.

3

Click Test Connection. Mattering lists the sites the token can reach and confirms it authenticates.

4

All 37 Webflow nodes appear in the canvas palette. Run Webflow: List Sites first: a site token returns exactly its one site, and the site id it returns is what almost every other node needs.

Common uses for the Webflow MCP

Page SEO metadata rewritten at scale

Webflow: List Pages inventories every static and template page with its current SEO and Open Graph settings, and Webflow: Update Page Metadata rewrites titles and descriptions per page. The changes are staged until the next publish, so an agent can rewrite fifty meta descriptions and a person can review before anything reaches the live site.

Mattering records become CMS items, with a person before publish

Records in a Mattering database become staged items through Webflow: Create Collection Item (Staged), which touches only the design-time layer. A review task gates Webflow: Publish Collection Items, so nothing reaches visitors until someone approves the exact item ids.

Content audits an agent can run

Webflow: List Collection Items (Staged) and Webflow: List Live Items expose both layers, so an assistant can find items whose staged copy carries unpublished edits, drafts that never went live, and content that drifted from the source of truth. Webflow: Get Page Content reads a page's actual text nodes for audits of what the site really says.

Form submissions routed into work

Webflow: List Forms maps a site's forms and their fields, and Webflow: List Form Submissions pulls what visitors submitted, keyed by field name, ready to become tasks, records, or notifications. Webflow: Delete Form Submission handles spam cleanup and data-removal requests; the delete is permanent, so gate it.

Localization on secondary locales

Webflow: Get Page Content reads a static page's text and component nodes on any locale, and Webflow: Update Page Content (Secondary Locales) writes translated content into a secondary locale. Webflow documents that endpoint for localization only, so the default locale's static content stays designer-owned.

Ecommerce reporting without write risk

Webflow: List Orders and Webflow: Get Order read order details, totals, and fulfillment state for reporting and notification flows, and Webflow: List Products covers the catalog with every SKU and price. The connector ships ecommerce reads only: no node can fulfill, refund, or edit commerce data.

Example: Approved records in a Mattering database become staged CMS items, and a person decides what goes live

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a scheduled run reads records marked Approved from a Mattering database (for example articles with title, body, and slug fields).

2

Webflow: Get Collection (Schema) returns the target collection's field slugs and types, so each record maps onto fieldData with the right keys.

3

Webflow: Create Collection Item (Staged) writes each record as a staged item. Nothing changes on the public site.

4

A review task in Mattering Productivity lists the staged item ids and titles for a person to approve.

5

Webflow: Publish Collection Items runs only after approval, promoting exactly the approved ids to the live site.

6

Webflow: List Live Items confirms the items are live, and the database records are marked Published so the sweep never repeats them.

Webflow MCP questions, answered

What Webflow operations are supported?

37 nodes on the Data API v2: sites and custom domains, site publishing, CMS collections with full field schemas, staged and live collection items (create, update, publish, unpublish, delete), page metadata and localized page content, forms and form submissions, asset reads, webhook management, and ecommerce product and order reads. Deliberately not shipped: asset upload (a multipart handshake an automation canvas cannot honestly produce, so assets are read access with CDN URLs), collection and field creation or deletion (schema design work, not an automation loop), ecommerce writes (refunds move real money), and Webflow's discontinued User Accounts, which no longer exist in the current API.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

What is the difference between staged and live items?

CMS items exist in two layers. The staged layer is the design-time copy: Webflow: Create Collection Item (Staged) and Webflow: Update Collection Item (Staged) change it without changing what visitors see. The live layer is what is published: Webflow: Publish Collection Items promotes chosen staged items to it, while Webflow: Create Live Item (Publishes Immediately) and Webflow: Update Live Item (Publishes Immediately) skip the staging step and change the public site in the same call. Unpublishing is not deleting: Webflow: Unpublish Live Item removes the live copy while the staged copy survives as a draft, and Webflow: Delete Collection Item is the permanent delete, with no undo via the API.

Can an automation change my live site by accident?

Not silently. The default CMS write path is staged and publicly invisible, and every node that changes the live site says so in its name or description. The one to treat with the most respect is Webflow: Publish Site: it pushes all staged changes, design and content alike, to the selected domains, there is no API rollback, and Webflow allows one successful site publish per minute. Keep it, and the live-item write nodes, behind a condition, an approval step, or a manual run.

Can a Webflow form submission or order trigger a workflow?

Not as an inbound trigger node in this connector. The webhook nodes manage registrations: Webflow: Create Webhook points Webflow's events (form submissions, site publishes, item lifecycle changes, orders, and more) at any URL you operate, and receiving those calls is the target URL's job. The polling alternative is a scheduled Webflow: List Form Submissions or Webflow: List Orders sweep that acts on what changed.

What are Webflow's rate limits?

60 requests per minute on Starter and Basic site plans, 120 per minute on CMS, Ecommerce, and Business plans, and custom limits on Enterprise, shared across all nodes on a credential. Webflow answers 429 with a Retry-After header when the budget is exhausted. Site publishing has its own limit of one successful publish per minute.

Can I upload assets through this connector?

No. Webflow's asset upload is a two-step multipart handshake (file metadata first, then a direct binary upload), which is the class of plumbing an automation canvas cannot honestly produce, so it is omitted rather than half-shipped. Webflow: List Assets and Webflow: Get Asset expose the asset ids and CDN URLs that CMS image fields and downstream steps actually need; upload new files in the Webflow designer.

Why might Webflow: Create Webhook fail with a site token?

Webflow's own documentation disagrees with itself here: the API reference marks webhook creation as requiring an OAuth app token, while the webhooks guide documents site tokens as supported and describes site-token webhooks receiving their own signing secret. The node is built per the guide, which is the newer document. If a site token receives a 403 from it, create the webhook in the Webflow dashboard instead; note that Webflow: List Webhooks may not show dashboard-created webhooks, since Webflow documents that list as app-created registrations.

37 nodes waiting on the canvas

Put Webflow to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Webflow is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products