Skip to content
All documentation
Publishing channels · Webflow
Summarise with

Publish to your Webflow CMS

Connect a Webflow CMS collection and CiteAgentic creates each approved piece as an item in it, with the body written into your Rich Text field. No OAuth app, no custom code.

Open Site Settings
You need a Webflow site on a plan that includes the CMS, and permission to generate a Site API token.

How it works

CiteAgentic calls the Webflow Data API v2 and creates one CMS item per approved draft. Webflow requires every item to carry a name and a slug; both come from the draft title. The body is written as HTML into a Rich Text field you nominate.

New items can be created staged or live. Staged items exist in the CMS immediately but only appear on the site at the next site publish, which is the safer default when someone reviews content before it ships.

What you'll need

  • A Webflow site with the CMS enabled and at least one collection to publish into.
  • A Site API token with CMS read and write scope.
  • The collection ID of the target collection.
  • The field slug of the Rich Text field that holds the body.

Step 1 — Generate a Site API token

  1. In Webflow, open Site settings → Apps & integrations → API access.
  2. Click Generate API token.
  3. Give it CMS read and write scope.
  4. Copy the token. Webflow shows it once.

Step 2 — Find the collection ID

Open the collection in the Designer's CMS panel, or open its settings. The hex string in the collection URL is the ID, for example 580e63fc8c9a982ac9b8b745.

Step 3 — Find the body field slug

A field's slug is the API name, which is not always the label you see in the Designer. A field labelled "Post Body" usually has the slug post-body. Open the collection's field settings to confirm it. CiteAgentic defaults to post-body.

The body field must be a Rich Text field. A plain-text field will store the HTML as visible markup rather than rendering it.

Step 4 — Connect it in CiteAgentic

  1. Open Site Settings → Publishing channels.
  2. Click + Webflow and fill in:
    • CMS collection ID — from step 2
    • Body field slug — from step 3, defaults to post-body
    • Published site URL — optional; lets CiteAgentic link to the item once it is live
    • Publish as — staged or live
    • Site API token — from step 1
  3. Click Test & connect.

The connection test reads the collection and warns you about any required fields it will not be filling. That warning matters: Webflow rejects an item that is missing a required field, so a collection with a required "Featured image" or "Author" reference needs a default set in Webflow before publishing will succeed.

Publishing

  • On demand: Share ▾ → Publish on any approved draft.
  • Automatic: link the Webflow channel to a day in the content calendar.

Frequently asked questions

Why did publishing fail with a validation error?
Almost always a required field on the collection that CiteAgentic does not fill, or a slug that already exists. The error message names the specific field, because we read Webflow's details array rather than only its generic message.
Staged or live?
Staged creates the item in the CMS without putting it on the site; it appears at the next site publish. Live publishes immediately. Choose staged if anyone reviews content before it ships.
Can I publish into more than one collection?
Yes. Add one Webflow channel per collection; each carries its own collection ID and body field.
Does the body arrive as Markdown or HTML?
HTML, written into the Rich Text field. Point the body field at a Rich Text field, not a plain-text one.

Ready to connect?

Site Settings → Publishing channels → + Webflow. Add your collection ID, body field slug, and a CMS read-write token.

Go to Site Settings