Webflow

Ownership and availability#

You own the Webflow site, Collection, and site token. Obelo encrypts the token and publishes only to the configured Collection.

Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.

CMS publishing requires an active Starter Pro plan or higher.

Before you connect#

• Site administrator access is required to generate a site token
• A CMS Collection with fields for title, slug, body, and publication state
• The site plan must support the CMS and publishing workflow you intend to use

Connect an existing account#

1. Open the provider in Settings → Integrations for the intended website.
2. Generate a site token from Site settings → Apps & integrations → API access
3. Grant CMS read/write and Sites read-only access
4. Copy the site URL, token, and Collection ID into Obelo for validation

If you need a new resource#

1. Create a Webflow site and add a CMS Collection for articles or pages
2. Define the Collection fields and publish the initial schema
3. Generate a site-specific API token with the minimum required scopes

Permissions to check#

• CMS read/write lets Obelo create and revise Collection items
• Sites read-only lets Obelo verify the site without changing global settings

Verify and troubleshoot#

Return with the published site URL, site token, and target Collection ID.

No usable CMS Collection was found. Create or publish a Collection, verify the Collection ID and token scopes, then check again.

Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.

Disconnect or change access#

Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.