webflow_* MCP tools — so a person, an automation and the AI all pass the same permission, confirmation and locale gates, and land in the same audit log.
Two ways Webflow shows up in Hiveku
One connection model, two altitudes. Connect once and use it either way.Account-level connection
Connect a Webflow account at
/dashboard/projects/settings/webflow. The hub lists every connection with its sites, the projects bound to each site, and Connect, Paste a site token, Reconnect and Disconnect. The first connection becomes the account default, and every project inherits it.Per-project binding
Each project picks its site and its connection under Settings in the Webflow workspace: inherit the account default, override with a specific connection and site, or turn Webflow off for that project. The same panel chooses whether new content is written to the Hiveku CMS or the Webflow CMS.
These are not two integrations. A project on inherit uses the very same account-default connection, so a Webflow account you connect once is available at both altitudes. Resolution is
override first, then the account default, then nothing; disabled hides the account default from that one project.Who it is for
- Teams with a Webflow site they like who want AI-written CMS content, SEO applied at scale, and form submissions in a CRM, without rebuilding the site.
- Agencies running several Webflow sites in one workspace, where each project needs its own connection and its own site.
- Marketing operators who need automation on top of Webflow: a workflow that fires on a form submission, a published item, a page metadata change or a site publish.
What Hiveku changes, and what stays in the Designer
This is the honest split, and it is the same split the product states inside the workspace.
The AI holds the same line. Ask the Webflow chat to move a section, restyle a hero or add a page and it refuses in plain words, points you at the Designer for that site, and then offers the nearest thing it can do — a CMS item, a redirect, an SEO change, a script.
Area by area, with the precondition
Staged and live. Most writes land on the staged site and become visible when you publish. Two exceptions are worth remembering: asset uploads and alt text apply immediately with no publish, and publishing a single CMS item makes that item live without publishing the whole site.
The workspace
A connected project gets a dedicated Webflow workspace at/<accountId>/dashboard/<projectId>/webflow — 27 routes behind a rail grouped as Site, Content, Engage, Code and config, and Workspace:
Rail items are never hidden by what your plan or connection allows — a page explains itself instead. Custom code and Webhooks carry a “Needs the full Webflow connection” marker on a site-token connection, and every Enterprise-only page has its own state rather than disappearing.
A collapsible AI chat pane sits on the left of the workspace, locked to Webflow mode. The mode dropdown stays visible and disabled with its reason on hover: this site lives on Webflow, so every change goes through the Webflow API. The composer only appears once the project has a connection and a site chosen; until then every turn is refused server-side.
Facts about the site — custom domains, locales, the live address, the last publish — come from a cached row rather than a live read on every page load, so each surface says when Hiveku last looked, and Settings carries a Refresh from Webflow action.
What the connection unlocks elsewhere
The Content department and New Content
Set the project’s content source to Webflow CMS and New Content, the Content department, the
cms_* tools and the CMS panel write your Webflow collections. Saving an entry stages it in Webflow; Publish makes it live.SEO applied to real pages
Page-SEO work from the SEO department is applied as a Webflow page metadata update instead of a source-file edit. Fields a Webflow page cannot hold — canonical URL, keywords, Twitter card, Open Graph image — come back reported as ignored, never silently dropped.
Forms, CRM and workflows
Hiveku registers its own receiver webhooks on each shared site. A routed submission lands in the Forms ledger, creates or updates a CRM contact, and can start a workflow with the Form Submitted trigger.
Automations
13 Webflow trigger nodes (site published, the collection item events, page events, comments, form submissions, and two catch-alls) and 110 Webflow action nodes, each also addressable as a
webflow_* MCP tool.One-click analytics
On an OAuth connection Hiveku installs its analytics tag as a registered inline script applied site-wide, and removes it the same way. It starts counting after the next publish.
Mobile
The iOS app carries the same Webflow site chat, overview and CMS screens, with the same capability wording. Connecting itself is done on the web.
The limit worth understanding before you start
Webflow’s Data API does not write page and component text in the site’s primary language. This is Webflow’s rule, not a Hiveku gap. Webflow states it in its localization documentation: API-based updates to page and component content are limited to secondary locales, and primary locale content for pages and components must be updated through the Webflow Designer. CMS item content is exempt — that works in both primary and secondary locales. There are three ways to work with this, in the order most teams should consider them:1
Bind the copy you rewrite often to a CMS collection
Anything bound to a Webflow CMS collection is fully editable through the API, in every locale. Moving your recurring copy — landing-page sections, testimonials, FAQs, feature blocks — into collections in the Designer once turns it into content the AI and the Content department can own from then on.
2
Add a secondary locale in Webflow
Add a locale under Localization in Webflow and page and component text becomes writable through the API in that locale only. The primary locale still belongs to the Designer.
3
Convert the site to a Hiveku-hosted project
The workspace’s Departments page ends with Convert to Hiveku-hosted, whose button takes you to Hiveku’s new-site flow: “Rebuild this site in Hiveku to edit layout and styles with the AI. Starts a new project; your Webflow site is untouched.” Nothing is imported from Webflow automatically — you build the Hiveku-hosted project the ordinary way, and the AI can then edit its layout and styles directly.
Two connection kinds
Fifteen of the 110 actions require an OAuth connection: the nine custom-code actions, the three page custom-code actions, creating and updating a webhook, and reading the authorizing user. Everything else works on either kind. Connecting has the full comparison and the exact refusal.
Where it lives
Next steps
Connect a Webflow site
The OAuth flow, what you approve, the site picker, the site-token alternative, and the one thing to do after connecting.
The workspace
The 27 pages, the rail, the left chat pane, and what each surface is for.
The AI chat
What to ask for, what the AI refuses on a Webflow site, and the words it uses when it does.
CMS and content
Pointing New Content, the Content department and the CMS panel at your Webflow collections, and what changes when you do.
Forms and events
Routing new submissions into the Forms ledger and the CRM, and importing the ones Webflow already holds.
Automations
The 13 trigger nodes, the 110 action nodes, confirm gates and dry runs.
SEO and analytics
The SEO grid, the page-SEO fixes the SEO department writes through Webflow, and the JSON-LD schema tab.
Limits
The primary-locale rule, what only the Designer can change, and the publish etiquette behind both.
For developers
The action registry and its four gates, the credential resolver, token encryption, the webhook receiver and the crons.