QuiboDocs
HomeSign in

getting started

Connect Webflow

API token + Site ID + Collection ID. We auto-detect your fields.

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.
  • An API token with the CMS: read and CMS: write scopes.
  • 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 and pick your workspace.
  2. Workspace settings, then Integrations, then the API access section.
  3. Click Generate API token and name it Quibo.
  4. Under scopes, check both CMS: read and CMS: write. Save.
  5. Copy the token (shown once).

Get the Site ID

  1. Open your project.
  2. Site settings (gear icon), General tab.
  3. Copy the Site ID at the top. It is also the <site-id> segment of the site dashboard URL, /sites/<site-id>.

Get the Collection ID

  1. In the Designer open the CMS panel (left sidebar, looks like a database).
  2. Hover the blog/posts collection and click the Settings icon that appears.
  3. Scroll to the bottom, open the API tab and copy the Collection ID (24 hexadecimal characters).

Plug it into Quibo

From Sites, then Connect a site pick Webflow and fill in:

  • Site name (e.g. Acme Blog)
  • Site URL, your published Webflow site (e.g. https://acme.webflow.io or your custom domain). Used to learn your brand voice.
  • Output language
  • API token
  • Webflow Site ID
  • Collection ID

Click Connect site. Quibo verifies the token and the Collection ID against Webflow before saving anything: if the check fails, nothing is stored and the error is shown in the wizard. Test connection on the site page stays available to re-check them later.

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 Rich Text field (commonly post-body or content).
  • Title and slug: Webflow auto-creates name and slug on every collection; we use those by default.
  • Fields: every field's slug, display name and type (Plain Text, Rich Text, Image, Reference, Multi-Reference, Date/Time, Switch, Option, Number). We only write fields your collection declares.
  • Reference targets: for every Reference or Multi-Reference field, we fetch the target collection's items (capped at 100 each). When the source field is called author, writer, byline or post-author, its items populate the Default author dropdown in the brand profile.

Discovery runs again once a day, or whenever you click Re-crawl brand on the site page.

Linking authors and categories

Webflow keeps collections isolated by default. To enable Quibo's author selection, add a Reference field to your blog posts collection:

  1. In the Designer open 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. Quibo lists the categories in the site schema but does not assign them to posts yet.

After saving, click Re-crawl brand on the site page (or wait for the daily refresh). The Default author dropdown then populates with your Author entries: pick one and click Save brand profile.

What we publish

For each article, Quibo POSTs to /v2/collections/{id}/items/live (creates and publishes in one call) and fills the fields it recognises:

  • name and slug: the article title and slug
  • One Rich Text field: the article HTML rendered from the editor (headings, lists, links, tables and the FAQ section). Quibo uses the body field found at discovery, else the field named after the body, content, article, post or main text, else the first Rich Text field. A Rich Text field named after a summary, excerpt, intro or teaser receives the meta description as one paragraph; every other Rich Text field is left untouched.
  • Plain Text fields named after the meta title (meta-title, seo-title): the SEO title
  • Plain Text fields named after the meta description, excerpt or summary (meta-description, seo-description, post-summary, excerpt): the meta description
  • Plain Text fields named after the social title or description (og-title, social-title, og-description, social-description): the social title and description, falling back to the SEO title and the meta description
  • Plain Text fields named after custom code, head code, embed or script: the JSON-LD as a complete <script type="application/ld+json"> tag. Fields named after JSON-LD, schema or structured data get the bare JSON, for a template that wraps it itself.
  • One Image field: the cover as { url, alt }, in the field named after the cover, hero, featured, thumbnail, main image or post image, else the first Image field. Other Image fields (an author photo, an OG image) are skipped. Webflow downloads the image from that URL.
  • A Reference field named author: the Default author you picked. A Plain Text field named author: the free-text byline.
  • Date/Time fields named after published, date or ending in -at: the publish time

Anything else (Switch fields like "Featured", Option fields, Numbers, Multi-Reference fields) stays empty for the editor to fill in Webflow.

When Quibo refreshes an article later, it PATCHes the same item (/items/{itemId}/live): the slug is kept and the date fields are left untouched, so the URL and the original publish date survive.

Test the connection

In Sites, then your site click Test connection: we hit /v2/collections/{id} to verify the token has the right scope and the Collection ID is valid. A 401 means the token was not copied in full or has expired. A 403 means the token is missing the CMS scopes. A 404 means the Collection ID is wrong (it's the long hex string 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. To connect with a new token, open the site page in Quibo, use Update credentials in the Credentials card, and the new values are verified against your CMS before they replace the old ones.