Publishing integrations

Webflow

Webflow has no fixed blog schema — every site names its fields differently — so the connection carries a mapping from our five concepts onto your collection’s own field slugs.

Create an API token#

  1. In Webflow, open the site’s Site settings → Apps & integrations.
  2. Under API access, click Generate API token.
  3. Give it the CMS capability with write access. Without cms:write the connection test fails with a 401.
  4. Copy the token. Webflow shows it once.

Find the collection ID#

  1. Open the CMS panel and select the collection you publish blog posts into.
  2. Open its settings. The collection ID is in the URL and on the settings panel — a 24-character hex string.
  3. While you are there, note the field slugs of the fields you use for the body, the summary and the main image. The slug is not the display name: a field called “Post Body” usually has the slug post-body.

Connect it#

  1. In Rankli, open Integrations → New integration → Webflow.
  2. API token and Collection ID from the two steps above.
  3. Site URL — optional, used only to show you where an item will be visible.
  4. Field mapping — defaults to Webflow’s own blog template. Change any that differ.
  5. Publish mode — live, or staged for review inside Webflow.
  6. Save. We fetch the collection and check every mapped field exists.
Our conceptDefault field slugType it must be
TitlenamePlain text
SlugslugSlug
Bodypost-bodyRich text
Summarypost-summaryPlain text
Imagemain-imageImage

A mapping that does not match the collection is caught when you save, not on the first article. The commonest cause of an opaque 400 at publish time is a rich-text field mapped onto a plain-text one — so we check the types up front.

What happens on publish#

We create a CMS item with the mapped fields. Images are handed to Webflow by URL and Webflow re-hosts them on its own CDN, so the item does not depend on our storage.

In live mode the item is published to the live site as part of the same call. In staged mode it appears in the CMS as a draft item and someone on your team publishes it.

Webflow’s CMS item limit is per plan. When you hit it, publishing fails with a clear message from Webflow rather than silently doing nothing — but it is worth knowing before you schedule thirty articles a month into a collection with room for ten.

When it does not work#

401 from Webflow

The token was revoked, or it lacks cms:write. Generate a new one with CMS write access.

404 on the collection

The collection ID belongs to a different site than the token does. Both must come from the same Webflow site.

The item published but a field is empty

That field’s slug in the mapping does not exist on the collection. Open the connection and compare it against the collection settings — the display name and the slug are different strings.

# Check a mapping without saving anything
rankli-cli integrations validate --provider webflow \
  --token "$WEBFLOW_TOKEN" --collection 66f1a2… --json