Getting there
The workspace lives at/{accountId}/dashboard/{projectId}/webflow. You reach it from the project switcher in the top-left of any project page: for a Webflow-connected site, Webflow is the first item in that menu, described as “Pages, CMS, assets, code and publishing on your Webflow site”.
The menu item only appears once
GET /api/builder/webflow/{projectId}/status answers with a connection, and only for external projects. It fails closed — no connection, no tab — so it never links you to a page that cannot load.1
Connect the site
Without a connection every panel is replaced by the connect card: “Connect with Webflow OAuth for the full API, or paste a site API token to start with content, CMS, assets and publishing.” Settings is the one route that bypasses the gate, so you can always get to it.
2
Pick which site the project uses
If the connection reaches more than one site, the workspace asks: “The connection reaches more than one site. Pick one in Settings so every page here targets it.” Until a site is bound, Publish is disabled with the hover reason “Pick a Webflow site in Settings to publish.” and the chat refuses every turn.
The layout
Three columns, left to right.Chat
The AI pane, on the left. Resizable between 360 and 640 px; its width and open state are remembered per browser, and it opens by default on screens 1280 px and wider. Toggle it from the header.
Rail
Sixteen destinations in five groups. Items are never hidden by capability — a page explains itself when it cannot do something.
Content column
The header, then the panel for the current route. The page itself never scrolls: the content column, the rail and the chat pane each scroll on their own.
The chat pane
The chat is locked to Webflow mode. The mode dropdown stays visible but disabled, with the reason on hover: “This site lives on Webflow, so every change goes through the Webflow API. Other modes need a Hiveku-hosted project.” That lock is enforced server-side too — a turn on a Webflow-bound project always runs the Webflow mode whatever the client asked for, and answers422 webflow_site_not_connected when no site is bound.
The mode’s permissions are read, MCP tools and publishing; file editing is off. The agent has no project files to write, and it is told to refuse and redirect rather than improvise: it cannot create, delete, rename or reorder pages, add, move or style elements, edit classes, components, interactions or variables, change page text in the primary language, author forms, or add locales. When you ask for one of those it says so and offers the nearest thing it can do — a CMS item, a redirect, an SEO change, a script.
Five starter chips seed the first turn:
- Draft 5 blog posts into the Blog collection
- Rewrite every page’s SEO title and description
- Add our GA4 tag to the site
- What changed since the last publish?
- Publish the site
The header
Domains, locales, the live address and the last publish time all come from a cached row rather than a live read, which is why surfaces say when Hiveku last looked (“Checked with Webflow 3 hours ago”). Settings carries Refresh from Webflow, which reports what changed — or “Refreshed from Webflow. Nothing had changed.”
The rail
Two markers appear on rail items, as icons with the text on hover: Needs the full Webflow connection on Custom code and Webhooks when the connection is a site token, and Not enabled on this site on Ecommerce when the site has no store. There is no Enterprise marker — nothing on the client knows the workspace plan, so each Enterprise-gated page explains it in its own empty state.
Area by area
Overview
“What Hiveku can see and change on this Webflow site. Pages, elements and styles stay in the Designer.” Overview carries the capability card — what is editable here versus what stays in the Designer — and seven health rows: Webflow connection working, All permissions granted, Custom code available, Page text editable here, Hiveku analytics installed, Review annotations enabled, Form submissions flowing to Hiveku. A row that is still loading reads “Checking”; a row whose check failed reads “Could not check right now”. A warning is only ever shown on a successful read that says something is wrong, never on a failed one.Pages and the page editor
“Titles, slugs, SEO and Open Graph are edited here. Pages themselves are created in the Webflow Designer.” The list shows every page with the badges that matter — a missing title, a missing description, changed since the last publish. Long sites are truncated with “Showing the first 2000 pages”. Opening a page gives you the editor on the left and a live preview on the right with a Staged / Live toggle, so you can see the version you are about to change beside the version visitors see. Four tabs, in this order:Settings — title, slug, SEO and Open Graph
Settings — title, slug, SEO and Open Graph
The page title, the slug, the SEO title and description, and the Open Graph title and description. These are the fields Webflow’s page-metadata endpoint holds, and they write the primary locale — no secondary locale is required.Changing a slug carries a warning it earns: “Changing the slug breaks inbound links. Webflow ignores slug changes on the home page, collection template pages and utility pages.”
Page code — page-level custom code
Page code — page-level custom code
Head and footer code for this one page. It needs an OAuth connection: on a site-token connection the tab still opens, marked Locked, with the reason “Page code needs a full Webflow connection. Reconnect with Webflow in Settings to use it.” Custom code runs only on the published site, so publish after changing it.
Text — body copy, secondary locales only
Text — body copy, secondary locales only
The page’s text nodes, as Webflow renders them. A write needs a secondary locale; on a single-locale site the tab shows the primary content as a readable list and one notice: “This site has one locale. Webflow’s API only writes page and component text in a secondary locale. Add one under Localization in Webflow, or edit this text in the Designer.”Text that comes from a CMS collection field is marked and kept read-only here — edit it on the collection item instead.
Schema — JSON-LD
Schema — JSON-LD
Structured data for the page, written to the primary locale. Hiveku checks Webflow’s own caps before the request rather than letting the API reject you: 60 KB of raw input, nesting depth 32, 5000 nodes, no closing script tag. Saved schema is staged: “Schema markup saved to the staged site. Publish to make it live.”
Components
“The text inside each component, as Webflow renders it. Components are built and styled in the Webflow Designer.” You can read every component’s text and properties, and write them in a secondary locale only — the same rule as page text. Components themselves are authored in the Designer.Publish
“Pushes the staged site to your domains. Visitors see the change within a minute. Webflow allows one publish per minute.” The page answers one question before you press anything: what has moved since last time. It shows when the site was last published, how many pages changed since, and which targets a publish would reach — “Publishes to example.com and www.example.com unless you pick other targets or a single page when you publish.”CMS
“Collections, fields and items on the Webflow site. Changes land on the staged site until you publish.” This is the fullest area in the workspace, and it is four screens deep.- Collections
- Fields
- Items
- One item
Every collection on the site as a card. New collection creates one with a display name, a singular name, a slug and optional starting fields. Renaming and deleting a collection live in the overflow menu on the collection’s own page; deleting asks you to type the name first, because it takes every item with it.
If this project’s content source is set to Webflow, the collections page carries a link across: “Also editable from the Hiveku content editor”. See Webflow as the content source for what that changes.
Assets
“Images and files in the Webflow asset library. Uploads and alt text apply immediately; the site does not need a publish.” Upload a file, import one from a URL, browse and create folders, and edit alt text. Two limits worth knowing: existing assets cannot be moved between folders through the Data API, and folders cannot be renamed, moved or deleted through it either.SEO
“Titles and descriptions on every page. Saved changes land on the staged site; publish to make them live.” A grid of every page with its title and description, counters for what is missing, and a deep link into a page’s Schema tab. The SEO department’s page-SEO fixes write through the same Webflow endpoint these fields use, so its work shows up here.Forms
“Forms are built in the Webflow Designer and their submissions are stored by Webflow. Import them here to see them in Hiveku Forms and the CRM.” Turn on routing and new submissions reach Hiveku as they arrive; Import brings the historical ones across. Routed submissions land in Forms, create or update CRM contacts, and can start workflows with the Form Submitted trigger. Imported historical rows deliberately start no workflow and send no notification.Webflow will not list a site’s forms until the site has been published at least once. Until then the page says so: “Publish the site once so Webflow can list its forms.”
Comments
“Read, reply to and resolve the review comments on this site. New comments can take up to five minutes to appear.” Threads and replies from Webflow’s own review comments. Replies post as the user who authorized the connection.Ecommerce
“Products, SKUs, stock and orders on your Webflow store. Currency, checkout, shipping and tax settings stay in the Webflow Designer.” Products and SKUs (names, slugs, prices and stock here; images, options and categories in the Designer), and orders — fulfil, unfulfil, refund and add tracking. If the site has no store the rail item is muted and the page says: “Turn on Ecommerce in the Webflow Designer to manage products and orders here.”Custom code
“Scripts Hiveku registers with Webflow and adds to the head or footer of the site, plus Google tags. Code pasted in the Webflow Designer or Site settings is separate: it stays where it is and does not appear here.” Four sections: registered scripts, applied site scripts, Hiveku snippets (one-click install for the analytics tag and the Review annotation bridge) and Google tags — GA4, Google Ads and Tag Manager ids Webflow loads on every page, up to 25. Custom code runs only on the published site, so publish after changes.Redirects and robots
“301 redirects, the robots.txt and llms.txt files and files under /.well-known/. Changes take effect on the next publish.”Webhooks
“Webhooks tell another system when something happens on this site, such as a form submission or a publish. Hiveku registers its own when it needs one. Only webhooks created through this connection are listed.” Webflow allows 75 registrations per trigger per site, and an identical registration is reused rather than duplicated. Registering a webhook needs an OAuth connection.Departments
“Where each Hiveku department meets this Webflow site. Content, SEO and publishing go through the Webflow API; design changes stay in the Designer.” One card per department that works on a Webflow site — SEO, Content, PPC, Reputation, Analytics, Review and annotate, Tasks, Automation — each linking straight to that department with this project in hand. The last card is Convert to Hiveku-hosted: “Rebuild this site in Hiveku to edit layout and styles with the AI. Starts a new project; your Webflow site is untouched.” Its button, Start a Hiveku-hosted site, opens Hiveku’s ordinary new-site flow — nothing is copied across from Webflow for you.Activity
“Who changed what on this site, and when. The site log tab shows the record Webflow keeps for Enterprise workspaces.” Two tabs. Hiveku and Webflow lists writes made from this workspace, the chat and the MCP tools, alongside the events Webflow sent Hiveku — publishes, CMS changes, form submissions. An event whose signature did not match is shown with an Unverified pill and was recorded but never acted on. Site log is Webflow’s own record and needs an Enterprise workspace.Settings
“How this project connects to Webflow, which site it works on and where new content is written.” Five sections: Connection (which Webflow account and site), Site (what Hiveku last read, plus Refresh from Webflow), Content source (Hiveku CMS or Webflow CMS — see the content-source page), Advanced (inherit the account default, override for this project, or turn Webflow off; plus granted permissions) and Disconnect.Publish etiquette
Almost everything you change in this workspace lands on the staged site and waits. Publishing is the separate, deliberate act that puts it in front of visitors.What needs a publish, and what does not
The CMS row is the one that surprises people. Saving a collection item stages it; publishing that item makes it live on its own, without a whole-site publish. Everything page-level waits for the site.
The three rules
1
One publish per minute
Webflow allows one successful publish per minute per site. Hiveku claims that minute locally and shows a countdown rather than letting you fire a second one: “Webflow allows one publish per minute. Try again in 41s.” An agent that hits it reports the wait instead of retrying.
2
A publish pushes everything currently staged
A site publish ships every staged change on the site, not only yours — including work a teammate or an agent staged and has not mentioned. Check the Publish page’s “changed since the last publish” count before you press it, especially on a shared site.
3
You choose the targets
The modal defaults to every custom domain, or the
webflow.io subdomain when there are none. You can narrow it to specific domains, or tick Only this page to publish a single page. Visitors see the change within a minute.What stays in the Designer
The primary-language limit is Webflow’s, not Hiveku’s: the Data API writes page and component content in secondary locales only, and primary-locale page and component content has to be updated in the Designer. Adding a secondary locale under Localization in Webflow unlocks that text — in that locale. CMS items are unaffected either way, and so are page titles, SEO and JSON-LD, which Hiveku writes to the primary locale.
If a site needs the AI to change layout and styling, the shipped answer is Convert to Hiveku-hosted on the Departments page. Its button opens Hiveku’s new-site flow; nothing is imported from Webflow automatically, so you build the Hiveku-hosted project the ordinary way and the Webflow site is left untouched.
A Designer panel that would close the primary-locale gap from inside Webflow is being explored. Nothing is built or scheduled, and nothing about it should be planned around.
What’s next
Webflow as the content source
What changes when a project writes its content into Webflow collections, and the round trip a writer experiences.
The Hiveku CMS
The file-based CMS a Hiveku-hosted project uses, and the features the Webflow CMS trades away.