> ## Documentation Index > Fetch the complete documentation index at: https://docs.hiveku.com/llms.txt > Use this file to discover all available pages before exploring further. # Webflow Overview > Keep your site in Webflow and run it from Hiveku: connect once and the AI, the departments, the workflows and the MCP tools drive the site's CMS, page metadata, SEO, assets, custom code, forms, comments, ecommerce and publishing through the Webflow Data API. Hiveku's Webflow integration is for teams who already have a Webflow site and are not moving it. You connect the site once, and Hiveku gets the same reach over it that it has over a Hiveku-hosted project: the AI chat, the Content and SEO departments, workflows, the MCP tools, analytics and the Forms and CRM ledgers all point at your Webflow site instead of at a codebase. Nothing is migrated. Every write goes to the Webflow Data API v2 against your own site, and reads come from Webflow or from a short-lived cache of what it last answered. Hiveku keeps a connection row, a cached site snapshot, an inbound event log, an index of the site's pages for Review, and a CMS read cache — never a second copy of your content you have to keep in sync. Webflow stays the source of truth, and your Designer, your styles and your published site are untouched by the connection itself. The surface is deliberately concrete: **110 actions**, one per capability, nine of them served by Webflow's beta namespace. One registry backs three surfaces — the Webflow workspace, 110 workflow action nodes, and 110 `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. 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. 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. | Here in Hiveku | In the Webflow Designer | | ----------------------------------------------- | ----------------------------------------------------- | | CMS collections, fields and items | Layout, elements, classes and styles | | Page titles, slugs, SEO and Open Graph | Creating, deleting, renaming or reordering pages | | Images and files, including alt text | Building and styling components | | Custom code, registered scripts and Google tags | Interactions and variables | | Form submissions, comments and orders | Authoring forms | | Publishing | Page text in the primary language, and adding locales | 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 | Area | What Hiveku changes through the Data API | Precondition | | ------------------------------------------------ | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | CMS | Collections, fields, items; staged and live | None | | Pages | Title, slug, SEO title and description, Open Graph, JSON-LD schema | Publish the site to make it live | | Page and component body text | The text nodes on a page or component | A **secondary locale** on the site | | Assets | Upload, alt text, metadata; listing and creating asset folders | Applies immediately; no publish needed. An existing asset cannot be moved between folders, and folders cannot be renamed, moved or deleted | | Custom code | Registered scripts, site head and footer code, Google tags | Scripts need an OAuth connection; Google tags work with a site token | | Forms | List forms, read, update and delete submissions, route new ones into Hiveku | Webflow lists a site's forms only after one publish, and routing new submissions needs an OAuth connection, because it registers a webhook | | Comments | Read threads, reply, resolve | Replies post as the user who authorized the connection | | Ecommerce | Products, SKUs, inventory, orders, fulfil, unfulfil, refund | Ecommerce enabled on the Webflow site | | Redirects, robots.txt, llms.txt, `/.well-known/` | Create, update and delete; well-known files are create and delete only | A Webflow **Enterprise** workspace | | Site activity log | Read the record Webflow keeps | A Webflow **Enterprise** workspace | | Publishing | Publish to the site's custom domains, or the `webflow.io` subdomain when there are none | Webflow allows one publish per minute | **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 `//dashboard//webflow` — 27 routes behind a rail grouped as Site, Content, Engage, Code and config, and Workspace: | Group | Pages | | --------------- | -------------------------------------------------------- | | Site | Overview, Pages and the page editor, Components, Publish | | Content | CMS collections, fields and items; Assets; SEO | | Engage | Forms, Comments, Ecommerce | | Code and config | Custom code, Redirects and robots, Webhooks | | Workspace | Departments, Activity, Settings | 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](/integrations/webflow/ai-chat) 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 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. 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. 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. 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. 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. 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. On a single-locale Webflow site, Hiveku cannot rewrite the body copy sitting directly on a page or inside a component. It can still change that page's title, slug, SEO title and description, Open Graph fields and JSON-LD, because those go through a different endpoint that writes the primary locale. There are three ways to work with this, in the order most teams should consider them: 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. 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. 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. A Designer panel that would close the primary-locale gap is being explored. Nothing ships today, and there is no date. ## Two connection kinds | | Webflow OAuth connection | Pasted site API token | | --------------------------- | --------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | Covers | The whole surface: CMS, pages, SEO, assets, forms, comments, ecommerce, publishing, custom code, webhooks | Everything except the fifteen OAuth-only actions: CMS, page titles and SEO, assets, forms, comments, ecommerce and publishing | | Custom code and scripts | Yes | No — refused with a clear message, not a broken tool | | Webhook registration | Yes, so inbound events and form routing work | No — Webflow refuses it, so you route form submissions by hand or reconnect with OAuth | | One-click analytics install | Yes | No — Hiveku gives you the tag to paste and cannot verify it | | Google tags | Yes | Yes | | Inbound delivery check | Webflow's HMAC signature plus a per-connection URL secret | The per-connection URL secret alone | 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](/integrations/webflow/connecting) has the full comparison and the exact refusal. ## Where it lives | Surface | Path | | ------------------------------------------------ | ----------------------------------------------------- | | Account-level Webflow hub | `/dashboard/projects/settings/webflow` | | The Webflow workspace | `//dashboard//webflow` | | Project connection, site and content source | `//dashboard//webflow/settings` | | Publish | `//dashboard//webflow/publish` | | Inbound receiver (Hiveku registers this for you) | `/api/webhooks/webflow//` | ## Next steps The OAuth flow, what you approve, the site picker, the site-token alternative, and the one thing to do after connecting. The 27 pages, the rail, the left chat pane, and what each surface is for. What to ask for, what the AI refuses on a Webflow site, and the words it uses when it does. Pointing New Content, the Content department and the CMS panel at your Webflow collections, and what changes when you do. Routing new submissions into the Forms ledger and the CRM, and importing the ones Webflow already holds. The 13 trigger nodes, the 110 action nodes, confirm gates and dry runs. The SEO grid, the page-SEO fixes the SEO department writes through Webflow, and the JSON-LD schema tab. The primary-locale rule, what only the Designer can change, and the publish etiquette behind both. The action registry and its four gates, the credential resolver, token encryption, the webhook receiver and the crons.