Webflow

Connect your sites — sign in to Magister, choose your brand, and open its Integrations panel. Select Webflow, continue to Webflow, and authorize only the sites you want Magister to use. You can also begin at Connect Webflow. OAuth availability is shown there. Canceling consent leaves existing connections unchanged.

Accounts and pricing — you need a Magister workspace and access to the Webflow site. Webflow features and CMS limits depend on your Webflow plan. Magister subscriptions and usage are billed separately; see pricing for current plans, trial terms, and included credits. Connecting Webflow does not purchase either subscription.

What Magister can do — read site, page, collection, and item metadata; prepare and edit CMS items using your collection’s actual fields; update page SEO and Open Graph metadata; and publish changes after approval. It does not provide the Webflow Designer or arbitrary layout editing. CMS Rich Text fields take HTML, and required fields vary by collection.

Start with a draft — ask “List my connected Webflow sites and their CMS collections,” then “Create a draft in this collection using these fields.” Identify the site and collection before changing content. Review the draft before asking Magister to publish it. A whole-site publish can also publish other staged changes, so confirm the destination and scope first.

Permissions — site read/write permissions support discovery and approved publishing; page read/write permissions support page metadata and SEO; CMS read/write permissions support collection discovery and content changes. The OAuth app does not request access to forms, ecommerce orders, assets, custom code, or your account profile.

Multiple sites — name the target site when asking for changes. Existing Webflow Sites API-token connections remain separate; a site-specific token takes precedence for that site. If overlapping OAuth connections are ambiguous, disconnect them and reconnect the intended sites.

Disconnect — use Disconnect on the Webflow card. Magister asks Webflow to revoke that authorization, then removes the matching stored credential and discovery metadata, including copies of that same token used in other Magister brands. Site-token connections remain separate. A failed provider revocation is shown as a disconnect failure so you can retry. You can also uninstall from Webflow; Magister removes the token after a failed authorization check or a provider 401 response. Background checks are bounded, so uninstall detection is not immediate.

Troubleshooting — reconnect after changing site access, or if Webflow reports an expired or revoked connection. A missing site or CMS collection can mean insufficient Webflow permissions. Contact team@magistermarketing.com for help.