Resources · Claude connector

Claude Webflow connectorWhat Claude can do in your Webflow account.

The Claude Webflow connector exposes 34 tools: 6 read, 28 write. Claude can build sections and components, fill CMS collections, fix SEO metadata and publish a site, inside the roles you already hold. Below: every tool, what needs the Designer open, and the guardrails.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Claude Webflow connector changes on a real site

You describe the change and Claude makes it in your actual Webflow project, working from the styles, variables and CMS already there. Webflow built the connector on its own APIs, so a hero section, a batch of blog posts or a round of meta descriptions happens in the conversation instead of a long session in the Designer.

Build a section from a sentence. Ask for a responsive hero with a headline and a call to action: data_element_builder creates the elements and data_style_tool applies classes you already use.

Run the CMS at scale. data_cms_tool creates collections and fields and updates items in bulk, saved as drafts until you publish them.

Fix SEO page by page. data_pages_tool reads and rewrites page SEO metadata and JSON-LD, and data_sitemap_tool decides what appears in the sitemap.

Where it stops matters. Claude never goes beyond your own role, cannot add users or change access, and cannot touch Classic interactions. Uploading an image by URL and the live Designer tools go through an open Designer session. Page branches and Analyze data depend on your Webflow tier or add-ons. And nothing runs by itself: no page updates when a form comes in. For event-driven flows, an automation tool does that job; see the Webflow n8n integration or the Webflow Make integration.

Vocabulary

Five words before you connect Webflow

The Claude vocabulary around this connector, in one minute.

Connector
The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
Tool
One named thing the connector lets Claude do. Claude picks what it needs by itself; the directory lists all 34 by name.
Authorization
Webflow's own screen, where you pick the sites and the workspace Claude may reach. Given once per person, and revocable.
Approval
The confirmation Claude waits for before it changes something on your site, shown in the conversation when it matters.
MCP
The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Webflow.
Connect

Connect Webflow to Claude in three steps

  1. 01

    Find Webflow in Claude

    Open Claude's settings, go to Customize then Connectors, and look up Webflow. On a Team or Enterprise workspace, an Owner or Primary Owner must enable it before members can each sign in.

  2. 02

    Start the connection

    Click Connect on the Webflow row and log in to Webflow in the window that Webflow opens itself. If the link breaks later on, Disconnect and connect again.

  3. 03

    Choose sites on the authorization screen

    Webflow's screen, not Claude, sets what the access covers. Select the sites and the workspace Claude may reach, then confirm. Access can also be withdrawn later from Webflow itself.

Tools

The 34 tools, split by what they do

Webflow gives Claude 34 tools: 6 that read your account, 28 that change something in it.

Webflow labels each tool itself as reading, writing or both. Any tool that can write sits in the write group, even if it also reads. Names stay exactly as Claude shows them.

  • 6 read
  • 28 write

What Claude reads (6)

6 tools

Six tools that look, measure or guide, and leave your site as it is.

ask_webflow_ai

Puts a free-form question about the Webflow API to Webflow's own AI and brings the answer back into the conversation.

When it helps
Claude hits a permission error on a collection and needs Webflow's view of what could cause it.
Watch out
it answers questions about the API, not about your content.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_analyze_tool

Reads Webflow Analyze data: traffic over time, ranked pages and ranked dimensions, engagement events and time on page. Webflow describes it as read only access.

When it helps
you want to know which pages drove last month's traffic before choosing what to rewrite.
Watch out
it needs the optional Analyze add-on on the Webflow side.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

element_snapshot_tool

Captures an image of an element as it looks on the canvas, so Claude can check its own work without publishing anything.

When it helps
Claude just built a pricing table and you want it to verify the layout on screen.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

get_asset_preview

Fetches an image preview of a site asset by its ID, the smallest variant or the original, up to 2 MB, images only.

When it helps
you ask which hero images are too heavy and Claude needs to look at them first.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

get_more_tools

Asks the server for a specialized tool when the ones already loaded do not cover a capability. It is how Claude reaches features outside the default set.

When it helps
a request touches a less common area of Webflow and nothing loaded fits.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

webflow_guide_tool

Returns Webflow's recommended workflows and best practices for using its tools, meant to be read before acting.

When it helps
before a large CMS job, Claude checks the order Webflow advises so it does not trip over a dependency halfway.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

What Claude changes (28)

28 tools

Twenty-eight tools that can alter your site, most of them reading too. No source describes a confirmation for any of them, so the general rule below applies.

asset_tool

Approval: see the rule

Uploads an image into your asset library from a public URL, during a Designer session. Every other asset task lives in the asset management tool.

What Claude asks for
no source describes a confirmation for this tool; the general rule below applies.
When it helps
a partner sent a logo link and you want it in your assets.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_agent_instructions_tool

Approval: see the rule

Manages a site's Agent Instructions, the rules and skills that tell agents how to work on it: they can point to the site's own variables, styles, components, pages and CMS collections.

What Claude asks for
nothing specific is documented; rely on the general rule.
When it helps
you want every agent to reuse your brand variables.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_assets_tool

Approval: see the rule

Handles a site's assets and folders: list, organize, update, delete, upload in two steps and compress oversized files.

What Claude asks for
no source says whether a prompt appears first; the approvals section covers it.
When it helps
your hero images are heavy and you want them compressed to WebP or AVIF.
Watch out
deletion is part of it.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_cms_tool

Approval: see the rule

Runs the CMS: collections, fields, field groups and items, created and updated as drafts; publishing them live is a separate step.

What Claude asks for
not documented for this tool; the general rule applies.
When it helps
forty blog posts lack a meta description and you want drafts in all of them.
Watch out
new localized items cannot be created, only existing ones updated.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_comments_tool

Approval: see the rule

Reads Designer comment threads and replies, filtered by page, status or date, looks up participants by email and posts replies.

What Claude asks for
no confirmation is documented; see the general rule below.
When it helps
a client left twenty comments on the staging site and you want them grouped and answered.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_component_builder

Approval: see the rule

Inserts component instances onto a page, inside an element or into a slot of another component, nested trees included.

What Claude asks for
the source is silent here, so the general approval rule applies.
When it helps
you want your testimonial card component dropped three times into the new landing page.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_component_tool

Approval: see the rule

Gets and queries components, creates blank ones, turns existing elements into components, and inserts or unlinks instances.

What Claude asks for
not documented; the general rule covers it.
When it helps
the same footer was rebuilt by hand on five pages and should become one component.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_element_builder

Approval: see the rule

Creates elements on a page from a schema, nested children included, in a single call. It is the main building tool behind a new section.

What Claude asks for
no source describes a confirmation; see the general rule.
When it helps
you ask for a three-column features block under the hero.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_element_tool

Approval: see the rule

Queries the element tree and modifies it: moves and removes elements, edits text, styles, links, images, heading levels and attributes.

What Claude asks for
nothing specific is documented; rely on the general rule.
When it helps
every third-level heading on a page should move up a level and nobody wants to click through them.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_enterprise_tool

Approval: see the rule

Manages enterprise site settings: 301 redirects, robots.txt, well-known files and site activity logs.

What Claude asks for
no confirmation is documented for this tool; the general rule applies.
When it helps
you restructured the blog and need redirects from the old URLs.
Watch out
a wrong robots.txt can hide a site from search engines.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_fonts_tool

Approval: see the rule

Manages uploaded custom fonts: list and inspect them, register new ones, replace their files, update metadata and remove them.

What Claude asks for
not documented here; see the general rule below.
When it helps
your brand switched typefaces and the old files must go.
Watch out
Google and Adobe fonts stay in site settings.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_forms_tool

Approval: see the rule

Reads forms and their schemas, lists and retrieves submissions site-wide or per form, and updates or deletes submissions.

What Claude asks for
no source describes a confirmation; the approvals section covers it.
When it helps
you want last week's contact requests summarized by topic.
Watch out
deleting a submission is part of its reach.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_localization_tool

Approval: see the rule

Localizes page and component content into secondary locales. It reads the primary or a secondary locale but writes only to secondary ones.

What Claude asks for
nothing is documented; the general rule applies.
When it helps
your French pages need their Spanish version drafted.
Watch out
new localized CMS items are out of scope.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_pages_tool

Approval: see the rule

Lists, creates and updates pages, manages page branches and their previews, and reads or writes SEO metadata and JSON-LD.

What Claude asks for
no confirmation is described; see the general rule below.
When it helps
ten landing pages share one lazy meta title.
Watch out
page branches depend on your Webflow tier.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_scripts_tool

Approval: see the rule

Registers, applies, updates and removes custom scripts at site or page level, and edits the head and footer code blocks.

What Claude asks for
not documented for this tool; the general rule covers it.
When it helps
you need a consent banner snippet added to every page.
Watch out
a broken script can affect the whole site.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_sites_tool

Approval: see the rule

Lists the sites you can reach, returns a site's details, and publishes a site to its domains.

What Claude asks for
nothing specific is documented; rely on the general rule.
When it helps
the fixes are done and you want the site live.
Watch out
this is the step that makes changes visible on your live domains.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_style_tool

Approval: see the rule

Creates, queries, updates, renames and removes classes and combo classes, and manages the variable modes applied to a style.

What Claude asks for
not documented; the general rule below applies.
When it helps
a dozen near-identical button classes should become one.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_variable_tool

Approval: see the rule

Creates, updates, renames and deletes variables for colors, fonts, numbers, percentages and sizes, and manages collections and modes.

What Claude asks for
no confirmation is documented; see the general rule.
When it helps
hardcoded colors and spacing should become variables you can change in one place.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_webhook_tool

Approval: see the rule

Lists, creates, retrieves and deletes a site's webhooks, the notifications Webflow sends to another service when something happens.

What Claude asks for
the source is silent on confirmation; the general rule applies.
When it helps
you want to see which old webhooks still fire after a tool change.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_whtml_builder

Approval: see the rule

Inserts elements onto a page from HTML and CSS strings, which lets Claude turn a snippet into native Webflow elements.

What Claude asks for
not documented for this tool; see the general rule below.
When it helps
a developer handed you a pricing block in HTML and you want it in the Designer.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

designer_tool

Approval: see the rule

Works with the open Designer: reads the current page, mode, branch, selection and breakpoints, selects elements, moves the canvas and creates page folders.

What Claude asks for
no source describes a confirmation; the general rule applies.
When it helps
you select a section and ask Claude to restyle that one.
Watch out
it works on the live Designer session, so the Designer has to be open.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_interactions_tool

Approval: see the rule

Creates and manages interactions built on GSAP, with their triggers and timelines, each set up in a single call. It runs without a Designer session.

What Claude asks for
nothing is documented here; rely on the general rule.
When it helps
you want cards to fade in on scroll.
Watch out
Classic interactions stay invisible to it.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_campaigns_tool

Approval: see the rule

Manages Campaign Hub sites, campaigns, page variations and their analytics. A campaign starts from a Markdown brief and produces a landing page.

What Claude asks for
no confirmation is documented; see the general rule.
When it helps
you want three personalized versions of a launch page.
Watch out
Early Access sites only.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_apps_tool

Approval: see the rule

Inspects and manages Webflow Cloud apps built from GitHub: environments, variable metadata, deployments, custom domains and logs.

What Claude asks for
not documented for this tool; the general rule applies.
When it helps
a deployment failed and you want its build log explained.
Watch out
secret values never pass through it.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_component_props_tool

Approval: see the rule

Manages a component's prop definitions and the values on its instances: create, update and remove props, set or reset values.

What Claude asks for
no source says whether a prompt appears; the approvals section covers it.
When it helps
your card component needs a new optional badge text.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_component_variants_tool

Approval: see the rule

Handles a component's variants and their scoped styles: create, duplicate, delete, reorder and rename variants, and set per-variant overrides.

What Claude asks for
nothing specific is documented; the general rule applies.
When it helps
your button needs a dark variant for the footer.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

data_element_settings_tool

Approval: see the rule

Covers element-level settings and data bindings: it reads and sets them, finds what an element can bind to, and sets its tag or visibility.

What Claude asks for
no confirmation is described; see the general rule below.
When it helps
a text block should pull the author name from the CMS instead of a fixed string.

Sourcedevelopers.webflow.com · September 30, 2026 ↗

Approvals

What Claude checks with you first

By default, Claude stops and asks before each action it takes on an account for someone. With 28 tools able to change a live site, including one that publishes, that default is worth keeping on.

On Team and Enterprise workspaces, owners decide whether members may let some actions run without a prompt each time. They can also limit what a connector may do across the organization, for example keeping reading on and writing off, and nobody overrides that from a personal account. Webflow adds its own rules: every agent works inside your existing roles and permissions, Agent Instructions steer how it builds, and each change lands in the site activity log.

Plans

Which plans include it

None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere, and that is a real gap in the catalog.

What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. Some Webflow features have their own conditions on Webflow's side, listed in the limits below. For the live state, check the Webflow sheet in the official directory. Only Webflow documents this connector.

Limits

Where the Webflow connector stops

A connector is not an automation. Claude calls these tools while it answers you, so nothing happens when a form is submitted or a CMS item goes stale.

Webflow says plainly that the server covers a focused set of its APIs, not all of them. Custom fonts mean uploaded files only; Webflow Cloud deployments need a GitHub-connected app and never handle secret values. The partner badge in the directory is not a security audit, and Anthropic states on every sheet that it neither picks the tools a publisher exposes nor guarantees they behave as announced. For a connector whose official sources contradict each other, see the Claude gmail connector.

Need help

Need help connecting Webflow to Claude?

A person reads every message.

FAQ

Questions about the Claude Webflow connector

01What can Claude do with the Webflow connector?
Claude can design, fill and maintain a Webflow site from the conversation. Its 34 tools cover building elements and components, styles and variables, the CMS, pages and SEO metadata, sitemap, forms, assets, fonts, custom code, redirects, interactions, localization, comments, Webflow Cloud apps, campaigns and publishing. Six tools only read, including site analytics, element snapshots and Webflow's guidance tools. Webflow labels each tool as reading, writing or both in its own documentation.
02Can Claude publish or delete things on my Webflow site?
Yes. The sites tool can publish a site to its domains, and several tools include deletion in their scope: assets, form submissions, styles, variables, webhooks and component variants among them. Webflow labels 28 of the 34 tools as able to write. What Claude cannot do is change access settings, add users or assign roles, and it never goes beyond what your own Webflow role allows. CMS items, by contrast, are saved as drafts, and publishing them live is a separate action.
03Does Claude ask before it changes my Webflow site?
By default, yes: Claude asks for confirmation before each action it takes on an account for someone. No source describes a specific confirmation for any single Webflow tool, so that default is what covers building, editing and publishing. On Team and Enterprise workspaces, owners decide whether members may skip some prompts, and they can block writing for everyone. Webflow also logs every agent change in the site activity log. You can review it at any time.
04Which plans is the Webflow connector available on?
No official source publishes plan availability connector by connector, and none of the directory's 819 sheets shows it. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them first on Team and Enterprise. Some Webflow features carry their own conditions on Webflow's side. The directory sheet shows the current state for your account.
05Can Claude reach every site in my Webflow account?
No. Claude reaches only the sites you select on Webflow's authorization screen, within a single workspace per authorization, and only site owners and admins can authorize a site. Inside those sites, Claude works with your existing Webflow role and nothing more. To reach another workspace, you remove and reinstall the connector. On Team or Enterprise, a Claude owner can also restrict the connector for the whole organization. Members cannot lift that restriction.
06Why can't Claude see or edit my site's interactions?
Most likely because your site still uses Classic interactions. Webflow's server can create and edit interactions built with GSAP, not Classic ones, so those stay out of reach. The interactions tool itself runs without a Designer session, so an open Designer is not the issue there. Uploading an image by URL and the live Designer tools, on the other hand, do need an open Designer session. If your site mixes both kinds, only the GSAP ones are reachable.
07Should I use Claude or an automation tool with Webflow?
They cover different needs. Claude with this connector is for building and maintaining on request: a new section, a CMS clean-up, an SEO pass, a publish when you say so. It stops when the conversation stops. If you want a CMS item created every time a form is submitted, or content synced from another app every night, that belongs to an automation tool reacting to events in the background. Both can work on the same site.