Webflow

Before you start — you need a Magister account and permission to authorize and manage the Webflow sites you choose. CMS work requires a collection and the Webflow plan permissions for your requested operation. Connect also requires an AI client compatible with Magister's MCP connector. Magister's interface and this guide are in English.

Set up your connection

One site per brand — a brand works with the one Webflow site you connected, and its website comes from that site, so there is no address to enter. To work on another site, add it as a new brand (available on paid plans; the price is shown before you confirm), or change the brand's site from Brand settings. Changing the site starts the brand over: Magister asks first, then erases what it built from the old site, including its plan, audits, chats, workflows, files and agent memory. It also revokes the old authorization in Webflow, then audits the new site and builds a new plan, which uses credits. A brand on its own domain that uses Webflow only as a CMS keeps that domain as its website.

Plans and pricing — Connect costs US$99/month with 5,000 credits for Magister tools in your external AI assistant; its subscription is separate, and Connect does not include a dedicated hosted agent. Agent costs US$199/month with 10,000 credits and includes Magister-hosted chat, a dedicated workspace, and Connect tools. The free trial includes 300 credits without a card. Each base plan includes one brand and 5 seats. Additional brands cost US$25/month on Connect or US$99/month on Agent; additional seats cost US$25/month. Additional usage can cost extra when enabled. Webflow and Magister subscriptions are separate, and connecting Webflow does not purchase a plan. See pricing for current offers and usage limits.

Draft and publish — ask Magister to list the selected site's collections, inspect a collection’s fields, and create a CMS draft. Review the draft, then request publication. Every publication or live-content change requires approval of that exact operation, including Auto mode and scheduled work. A whole-site publish may publish other staged changes; review the scope carefully. Generic MCP writes cannot bypass approval using a confirmation flag; use the publish_content tool for CMS publication.

Supported features — read sites, page metadata and content, collection schemas and items; create and edit staged CMS content; update page SEO and Open Graph metadata; publish with approval. Arbitrary Designer layout editing and design-token management are not supported. The OAuth scopes are sites:read/write, pages:read/write and cms:read/write. Forms, ecommerce orders, assets and custom code are outside this integration.

Localization — reads use the primary locale by default. Editing and publishing sites with secondary locales is not supported in this version, including whole-site publishing. Magister checks the site before changes and explains when you need to make the change directly in Webflow.

Optional audits and data access — Webflow content is retrieved through official Data API v2 endpoints: sites, sites/{id}/pages, pages/{id}/dom, sites/{id}/collections, collections/{id}, and collections/{id}/items. Audits use a bounded sample of up to 20 static pages and 10 collections with up to 100 items each, not a complete site export. Rendered HTML, robots, sitemap, performance and design-token checks are unavailable through this audit source. No public-page crawler, scraping service or manual token replaces OAuth if access fails or is disconnected. This covers every site built on Webflow, not just yours: Magister never reads one by fetching, crawling or scraping its public pages, custom domains included, even when you ask. A site is recognized as Webflow's by its address (*.webflow.io), by DNS pointing at Webflow hosting, or by the page's own Webflow marks, and that holds in chat, workflows, background work and audits: page-reading tools, research services, shell commands and the browser refuse it, results from it are dropped from web search, and a Webflow-built site gives no audit until its owner connects Webflow. The agent reads your connected site through these endpoints, and if Webflow is disconnected it tells you the site needs reconnecting. An external assistant's own browsing is outside these checks.

Where your content goes — Webflow page text, SEO metadata, collection schemas, and CMS item fields, including drafts, can become AI context for the requested task. While a site is connected, Magister can also review its CMS content about once a week to keep notes on what has worked for that brand; these reviews cannot publish or change anything. In hosted Agent chat or the free trial, relevant content is sent to the model serving the task, including configured fallback models. Automated audits, suggestions, and these reviews use task-assigned models on every plan, including Connect. Providers include Anthropic or OpenAI directly, or OpenRouter and its configured inference providers (Google Cloud Vertex AI, Fireworks AI, Together AI, Parasail, or Novita AI). With Connect, or Agent's MCP connector, requested Webflow tool results go to the external client you authorized, such as Claude or ChatGPT, under that client's own privacy and retention terms. A task follows its assigned model and any fallback routes; it is not sent to every provider. If you ask the assistant to use another connected service, the content you pass along goes to that service. Error reports sent to Sentry can include the request being processed, with credentials removed. See Webflow Site Content in our privacy policy for storage, retention, and deletion.

Saved copies and deletion — Magister can retain Webflow-derived content in conversations, audits, brand memory, marketing notes, approval records, and project files on Supabase and Fly.io. Disconnecting does not erase them; uninstalling does, as described below. Deleting a conversation from the sidebar removes database messages but leaves the Agent's local history and separately saved copies. Account deletion removes account-owned records and workspaces in organizations you created; other members' records and external-client copies can remain, and uploaded-file cleanup may require follow-up. Deleted content can remain in backups until they age out: about 7 days for the database and 5 days for Agent workspace snapshots. Contact support for removal of saved Webflow content. An optional SEO audit can send your domain and task-derived keyword or location queries to DataForSEO, as described in the privacy policy.

Disconnect — use Disconnect on the Webflow card. Magister immediately stops using Webflow for this brand. Disconnect ends this brand's link only: nothing is revoked in Webflow, Magister stays installed on the site, and other brands connected through the same authorization keep theirs. Magister keeps the authorization encrypted and unused, apart from checking that it is still valid, so Reconnect on the card restores the connection without authorizing again. A connection made from a share page comes back from that page. To connect a different site, use Connect a different site on the card, which goes through Webflow's authorization, as does connecting the site to another Magister organization, because nothing else proves that person may use it. Already dispatched requests may finish. Other providers are unaffected. Manual Webflow tokens are not supported and cannot be used as a fallback.

Uninstall — to remove Magister's access, uninstall it from the site in Webflow, under Apps & Integrations. Magister detects this on a provider 401 or a periodic authorization check, usually within a minute, stops all calls for that site, and erases the authorization. It emails your organization's owner the last day to keep it, about a week out, and after that day deletes what it holds for each brand that used that authorization: its plan, audits, chats, workflows, files and agent memory. The brand, its members and its other connections stay, as do the host names it connected, which are how Magister keeps refusing to read those sites' public pages. Until then, Keep this data on the Webflow card or connecting Webflow again cancels the deletion. Usage records for billing and the provider's ids for what was published stay, without the content. Deleted content can remain in backups until they age out, and copies in an external AI client stay with that client.

Content cleanup — disconnecting or uninstalling does not undo content you approved in Webflow. To remove a created article, open its collection in Webflow CMS, unpublish the item if it is live, then delete it. To revert page SEO, open that page’s settings in Webflow and restore the title and description you want. Publish the affected site when Webflow requires it to update the live page, then verify the public URL. Magister does not inject scripts or custom code. It cannot remove Webflow content after access is revoked; use Webflow’s own controls. For deletion of retained Magister account data, follow the privacy policy or contact support.

Troubleshooting — retry expired or canceled installation from Connect Webflow. Reauthorize when the chosen site is missing or access changes. Short rate-limit responses on reads are retried with bounded backoff and Webflow’s Retry-After delay. If rate limiting continues, retry later. An installation identity or site-discovery failure may require restarting Connect Webflow instead of displaying the retry delay. Writes are not automatically replayed. API failures never fall back to a crawler. Contact team@magistermarketing.com for help.