AI workers for Webflow

What is an AI worker for Webflow?

An AI worker for Webflow is an AI agent scoped to one job on the Webflow sites you authorized at connect time — syncing a CMS collection, drafting items on a cadence, tending page metadata, or acting as a canvas assistant while a designer works. It runs through Webflow's official MCP server, and every tool it may call, reading or writing, is granted individually when the worker is set up. Nothing is available to it by default.

What these workers do

Keep a CMS collection in step

Collection items get created and updated from the source of truth on a schedule — staged as drafts where review matters — without anyone re-keying fields.

Draft content on a cadence

New CMS items arrive written to the brief in the worker's instruction, ready for a person to review, with publishing kept as its own deliberate step.

Tend page SEO and Open Graph

Page titles, meta descriptions and social-preview settings get read, checked against the page, and updated where they have drifted.

Make publishing a scheduled decision

A worker holding only the sites tool publishes approved changes at the hour you chose — and nothing else, because that is all it was bound.

Assist live in the Designer

With the site's Designer open and the Bridge app connected, a worker can build elements, styles and components on the canvas as an interactive assistant — design-session help, not unattended automation.

How an AI worker runs in Webflow

Every tool is a separate grant

Two kinds of tools, honestly labeled

The sharp writes, named

What Webflow workers are actually for

Webflow questions, answered.

Which sites can a worker reach?

The sites you authorized on Webflow's approval screen when you connected — Webflow scopes the OAuth grant to a chosen site set, so a site you never authorized is not reachable at all. Each worker is then narrowed again to the tool families you bound to it, and every call it makes is logged with the site it touched. Authorizing more sites later means reconnecting deliberately, which is the right friction for widening reach.

Can a worker redesign our pages?

Only while a person has that site's Designer open with Webflow's MCP Bridge app — the canvas tools work through a live designer session, so they can assist during design work but cannot run unattended, and a scheduled worker that reaches one simply fails. Headless tools cover the content side: CMS items, page metadata, code and publishing. A kit promising automated redesigns would be overpromising, and ours do not.

Can it publish to the live site?

Only through the sites tool, which carries publishing, and only if you bound that tool to that worker. The clean shape is separation: drafting workers hold the CMS tool and stage items, and one deliberately-configured worker — or a person — holds the sites tool and makes things live. A worker without the sites tool can prepare everything and change nothing visitors see.

What is the riskiest tool here?

The custom-code tool, followed by webhooks. Registered scripts run on the live site for every visitor, which makes the code tool the sharpest write Webflow exposes, and a webhook subscription sends site events to whatever URL it names, which makes it an egress decision. Both ship enabled because the decision is yours, not the platform's — bind them only to workers whose job is explicitly code or integrations, and let the per-call audit log do its work.

Is there a record of what a worker did?

Yes, in two places. Every call a worker makes through this connection is logged with the worker, the tool and the time, reads and writes alike, so an item that changed overnight traces to the run that changed it. Webflow keeps its own trail too — item history, publish history and site activity — which shows the worker's changes alongside everything people did, and that second view settles whether it was the worker at all.

What AI workers can do in Webflow

The tools a worker can be granted in Webflow once you connect it. A kit grants only the ones its job needs, and you can narrow them further on the worker.

Asset tool

Manage assets from the open Designer session: files, folders and metadata such as alt text. Requires the site's Designer open with the MCP Bridge app.

Component builder

Build a component from a structural description on the open Designer canvas. Requires the site's Designer open with the MCP Bridge app.

Data cms tool

Webflow CMS: create, read, update and delete collections, fields and items — the whole structured-content lane, including staging items as drafts for later publishing. Localized items have vendor limitations.

Data comments tool

Comment threads on a site's Designer collaboration surface: read and manage them.

Data components tool

Site components over the Data API: list and manage component definitions and their content.

Data enterprise tool

Enterprise-plan APIs — available only when the connected Webflow workspace is on an Enterprise plan; calls fail politely otherwise.

Data pages tool

Pages: list them and read/update page metadata — titles, SEO and Open Graph settings. Static-page content updates are vendor-limited to secondary locales today.

Data scripts tool

Custom code on a site: list registered scripts and where they apply, register and apply inline code, and delete site scripts. Injected code runs on the live site — bind deliberately.

Data sites tool

Sites the connection can reach: list them, read settings, domains and configuration, and publish — one action-based tool for the site family. Publishing puts pending changes live to visitors.

Data webhook tool

Site webhooks: list, create and remove subscriptions for events like form submissions, CMS changes, orders and publishes. A created webhook sends site data to the URL it names — review targets carefully.

Data workflows tool

Webflow workflows (logic/automations) on a site: inspect and manage them.

De component tool

Create and manage components and their instances on the open Designer canvas. Requires the site's Designer open with the MCP Bridge app.

De page tool

Create and manage pages from the open Designer session. Requires the site's Designer open with the MCP Bridge app.

Element builder

Build multi-element structures on the open Designer canvas in one operation. Requires the site's Designer open with the MCP Bridge app.

Element snapshot tool

Read a snapshot of elements from the open Designer canvas — the read half of canvas work. Requires the site's Designer open with the MCP Bridge app.

Element tool

Live canvas editing: create and modify elements on the page a designer has open. Works only while that site's Designer is open with Webflow's MCP Bridge app — unattended runs will fail.

Get image preview

Fetch a preview image from the open Designer session — visual feedback for canvas work. Requires the site's Designer open with the MCP Bridge app.

Style tool

Manage styles and classes on the open Designer canvas, including responsive breakpoint values. Requires the site's Designer open with the MCP Bridge app.

Variable tool

Manage design variables (colors, sizes, fonts) on the open Designer canvas. Requires the site's Designer open with the MCP Bridge app.

Whtml builder

Compose page structure from an HTML-like description onto the open Designer canvas. Requires the site's Designer open with the MCP Bridge app.