Indexly

Webflow

Connect a Webflow site with a Site API token so Indexly Content Agents can create items in a CMS Collection — mapped to your own fields — and optionally publish them live.

What you can do

  • Create CMS Collection items from Content Agent articles
  • Map article fields (title, slug, body, excerpt, image) to your collection fields
  • Save as draft or publish live to your domain
  • Keep rich-text formatting, headings and internal links

Before you begin

  • A Webflow site on a plan that includes the CMS
  • A CMS Collection for your articles (e.g. Blog Posts) with at least a rich-text body field
  • A workspace role that can generate API tokens for the site (Admin on the site, or workspace Owner/Admin)

Create a Site API token

A Site token grants access to one Webflow site — no app install or OAuth authorization is involved.

  1. In the Webflow Designer or Dashboard, open the site's Site settings → Apps & integrations.
  2. Scroll to API access and click Generate API token.
  3. Name it Indexly and grant these scopes:
    • CMS — read and write (create collection items)
    • Sites — read (list collections and fields)
    • Sites — publish, only if you want Indexly to push items live
  4. Click Generate token and copy it. Webflow shows the token once — if you lose it, generate a new one.

Connect in Indexly

  1. In Indexly, open Integrations → Webflow and click Connect.
  2. Paste the Site API token and click Test connection. Indexly resolves the site the token belongs to and loads its collections.
  3. Choose the CMS Collection to publish into.
  4. Map your fields — match Indexly's article fields to your collection's fields:
    • Title → Name
    • Slug → Slug
    • Body → your Rich text field
    • Excerpt / meta description → your summary field
    • Featured image → your image field
  5. Choose whether items are created as staged (draft) or published live, then save.
One token, one site. A Site token only works for the site it was generated on. To connect several Webflow sites, generate a separate token for each and add them as separate connections.
Required fields matter. If your collection has required fields that aren't mapped, Webflow rejects the item. Either map them or make them optional in the Collection settings.

Troubleshooting

  • 401 unauthorized — the token was revoked, or it was regenerated in Webflow and the new value hasn't been pasted into Indexly. Generate a fresh token and reconnect.
  • 403 on create or publish — the token is missing a scope. CMS write is required to create items; Sites publish is required to push them live. Scopes are fixed at generation time, so generate a new token with the right scopes.
  • No collections listed — the token lacks Sites read, or it belongs to a different site than the one you expected.
  • Validation error on create — an unmapped required field, or a value that doesn't match the field type (e.g. plain text into a reference field).
  • Item created but not visible — it was staged. Publish the site in Webflow, or switch the integration to publish live.
  • Slug conflicts — Webflow slugs must be unique. Indexly appends a suffix when a collision is detected.
  • Rate limits — Webflow's API is rate limited; large backfills are queued and retried automatically.

Related