- Home
- Resources
- Integrations
- Webflow
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
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.
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 Webflow to Claude in three steps
- 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.
- 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.
- 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.
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
Tools index
- asset_tool
- data_agent_instructions_tool
- data_assets_tool
- data_cms_tool
- data_comments_tool
- data_component_builder
- data_component_tool
- data_element_builder
- data_element_tool
- data_enterprise_tool
- data_fonts_tool
- data_forms_tool
- data_localization_tool
- data_pages_tool
- data_scripts_tool
- data_sitemap_tool
- data_sites_tool
- data_style_tool
- data_variable_tool
- data_webhook_tool
- data_whtml_builder
- designer_tool
- data_interactions_tool
- data_campaigns_tool
- data_apps_tool
- data_component_props_tool
- data_component_variants_tool
- data_element_settings_tool
What Claude reads (6)
6 toolsSix 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.
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.
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.
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.
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.
webflow_guide_tool
Returns Webflow's recommended workflows and best practices for using its tools, meant to be read before acting.
What Claude changes (28)
28 toolsTwenty-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 ruleUploads an image into your asset library from a public URL, during a Designer session. Every other asset task lives in the asset management tool.
data_agent_instructions_tool
Approval: see the ruleManages 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.
data_assets_tool
Approval: see the ruleHandles a site's assets and folders: list, organize, update, delete, upload in two steps and compress oversized files.
data_cms_tool
Approval: see the ruleRuns the CMS: collections, fields, field groups and items, created and updated as drafts; publishing them live is a separate step.
data_comments_tool
Approval: see the ruleReads Designer comment threads and replies, filtered by page, status or date, looks up participants by email and posts replies.
data_component_builder
Approval: see the ruleInserts component instances onto a page, inside an element or into a slot of another component, nested trees included.
data_component_tool
Approval: see the ruleGets and queries components, creates blank ones, turns existing elements into components, and inserts or unlinks instances.
data_element_builder
Approval: see the ruleCreates elements on a page from a schema, nested children included, in a single call. It is the main building tool behind a new section.
data_element_tool
Approval: see the ruleQueries the element tree and modifies it: moves and removes elements, edits text, styles, links, images, heading levels and attributes.
data_enterprise_tool
Approval: see the ruleManages enterprise site settings: 301 redirects, robots.txt, well-known files and site activity logs.
data_fonts_tool
Approval: see the ruleManages uploaded custom fonts: list and inspect them, register new ones, replace their files, update metadata and remove them.
data_forms_tool
Approval: see the ruleReads forms and their schemas, lists and retrieves submissions site-wide or per form, and updates or deletes submissions.
data_localization_tool
Approval: see the ruleLocalizes page and component content into secondary locales. It reads the primary or a secondary locale but writes only to secondary ones.
data_pages_tool
Approval: see the ruleLists, creates and updates pages, manages page branches and their previews, and reads or writes SEO metadata and JSON-LD.
data_scripts_tool
Approval: see the ruleRegisters, applies, updates and removes custom scripts at site or page level, and edits the head and footer code blocks.
data_sitemap_tool
Approval: see the ruleReads and sets whether static pages and CMS items appear in the sitemap, one by one or in bulk.
data_sites_tool
Approval: see the ruleLists the sites you can reach, returns a site's details, and publishes a site to its domains.
data_style_tool
Approval: see the ruleCreates, queries, updates, renames and removes classes and combo classes, and manages the variable modes applied to a style.
data_variable_tool
Approval: see the ruleCreates, updates, renames and deletes variables for colors, fonts, numbers, percentages and sizes, and manages collections and modes.
data_webhook_tool
Approval: see the ruleLists, creates, retrieves and deletes a site's webhooks, the notifications Webflow sends to another service when something happens.
data_whtml_builder
Approval: see the ruleInserts elements onto a page from HTML and CSS strings, which lets Claude turn a snippet into native Webflow elements.
designer_tool
Approval: see the ruleWorks with the open Designer: reads the current page, mode, branch, selection and breakpoints, selects elements, moves the canvas and creates page folders.
data_interactions_tool
Approval: see the ruleCreates and manages interactions built on GSAP, with their triggers and timelines, each set up in a single call. It runs without a Designer session.
data_campaigns_tool
Approval: see the ruleManages Campaign Hub sites, campaigns, page variations and their analytics. A campaign starts from a Markdown brief and produces a landing page.
data_apps_tool
Approval: see the ruleInspects and manages Webflow Cloud apps built from GitHub: environments, variable metadata, deployments, custom domains and logs.
data_component_props_tool
Approval: see the ruleManages a component's prop definitions and the values on its instances: create, update and remove props, set or reset values.
data_component_variants_tool
Approval: see the ruleHandles a component's variants and their scoped styles: create, duplicate, delete, reorder and rename variants, and set per-variant overrides.
data_element_settings_tool
Approval: see the ruleCovers 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 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.
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.
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 connecting Webflow to Claude?
A person reads every message.


