Connect Webflow

Quibo connects to Webflow via the official v2 CMS API. You generate a token in your Workspace settings and paste three values into Quibo. We discover your collection schema (fields, types, reference targets) automatically and publish straight into the collection.

What you'll need

• A Webflow project with at least one CMS Collection for blog posts.
• A Workspace API token with CMS: read + write scope.
• The Site ID of your Webflow project.
• The Collection ID of the collection that should receive blog posts.

Generate the API token

1. Open workspace.webflow.com → pick your workspace.
2. Workspace Settings → Integrations (left sidebar) → API Access section.
3. Click Generate API Token, name it Quibo.
4. Under scopes, check both CMS: Read and CMS: Write. Save.
5. Copy the token (shown once, format 1a2b3c4d5e6f...).

Get the Site ID

1. Open the Webflow Designer for your project.
2. Designer → Site Settings (gear icon, top-left near the project name) → General tab.
3. Copy the Site ID at the top.

Get the Collection ID

1. Open the Designer → CMS icon (left sidebar, looks like a database).
2. Hover the blog/posts collection → click the ⚙ Settings icon that appears.
3. Scroll to the bottom → API tab → copy the Collection ID (24-char hex).

Plug it into Quibo

From Sites → New pick Webflow and paste:

• Site name (e.g. Acme Blog)
• Site URL — your published Webflow site URL (e.g. https://acme.framer.website or your custom domain). Used to extract your brand voice.
• API token
• Webflow Site ID
• Collection ID

Click Connect site.

Auto-discovery

When you connect, Quibo calls Webflow's GET /v2/collections/{id} to learn your collection's schema and discovers:

• Body field — the first RichText field (commonly post-body or content).
• Title + Slug — Webflow auto-creates name + slug on every collection; we use those by default.
• Fields — every field's slug, display name, type (PlainText / RichText / Image / Reference / DateTime / Boolean / Option / etc.). We only write fields your collection declares.
• Reference targets — for every Reference / Multi-Reference field, we fetch the target collection's items (capped at 100 each) so the Default author dropdown in Quibo's brand profile is populated automatically.

Linking Author + Categories

Webflow keeps collections isolated by default. To enable Quibo's author selection (and future category picker), add Reference fields to your blog posts collection:

1. In Designer → CMS → your blog collection → ⚙ Settings → Fields → + Add new field.
2. Type Reference → Source: your Authors collection → Field name: Author → Save.
3. (Optional) + Add new field → Type Multi-Reference → Source: your Categories collection → Field name: Categories → Save.

After saving, Quibo re-introspects automatically (or you can click Re-crawl brand on the site detail page) and the Default author dropdown populates with your Author entries.

What we publish

For each article, Quibo POSTs to /v2/collections/{id}/items/live with:

• name ← article title
• slug ← article slug
• The body field ← HTML rendered from the Tiptap document
• post-summary (or any string field with summary/excerpt name) ← meta description
• main-image / thumbnail-image (or any image field with image/cover name) ← { url, alt }
• author (Reference field) ← the Default author you picked
• published / date field (DateTime) ← now

Anything else (Switch fields like "Featured", custom Color fields, etc.) stays empty for the editor to fill in Webflow.

Test the connection

In Sites → your site click Test connection — we hit /v2/collections/{id} to verify the token has the right scope and the collection ID is valid. If you see a 403, the token is missing CMS scope. If 404, the Collection ID is wrong (it's the long hex from the Designer's API tab, not the collection's display name).

Security

• The API token is encrypted at rest.
• It's never returned to the browser, never logged, never sent to a third party.
• Revoke any time from your Webflow Workspace Settings → Integrations → API Access → revoke the token.