Webflow publishing

The Webflow adapter creates draft items in a CMS collection through the Webflow Data API v2. It works with any Webflow site that has CMS hosting.

How does Webflow publishing work?

CiteFlow authenticates with a Webflow API token and calls POST /v2/collections/{collection_id}/items with isDraft: true. Items land in the collection's Drafts tab and only go live when you publish the site from the Webflow Designer or admin.

What do you need before setting it up?

• A Webflow site with CMS hosting (Basic CMS plan or above).
• A blog (or article) collection with the field slugs listed in Required collection schema below.
• A Webflow workspace role that can generate API tokens (Workspace Admin or higher).

How do you set up Webflow publishing?

1. Generate the API token

1. In Webflow open your Site settings.
2. Go to Apps and integrations.
3. Scroll to API access and click Generate API token.
4. Name it (for example CiteFlow).
5. Grant scopes:
   • CMS → Read and Write
   • Sites → Read (used to verify the token during the connection test)
6. Click Generate and copy the token. Webflow shows it once.

2. Find your site and collection IDs

• Site ID: in Site settings → General, scroll to the bottom. The Site ID is shown as a 24-character hex string.
• Collection ID: in the Webflow Designer open the CMS panel, click the gear icon next to the collection name, then Collection settings. The Collection ID is shown at the bottom.

3. Required collection schema

The collection you publish to must contain the following field slugs. Slugs are case-sensitive and use kebab-case in Webflow.

If your collection uses different slugs (for example body instead of post-body), rename the fields in Collection settings → Fields so the slugs match. Webflow keeps the field labels separate from the slugs, so this does not affect your Designer UI.

4. Add the endpoint in CiteFlow

1. Dashboard → Settings → Publishing destinations → Add endpoint.
2. Pick Webflow.
3. Fill in:
   • API token: from step 1.
   • Site ID: from step 2.
   • Collection ID: from step 2.
4. Save.

5. Test the connection

Click Test connection. CiteFlow calls GET /v2/sites/{site_id} to verify the token, then GET /v2/sites/{site_id}/collections to confirm the configured collection_id belongs to that site. Both must succeed.

How do fields map to Webflow?

CiteFlow appends the article's JSON-LD schema as a <script type="application/ld+json"> block inside post-body because Webflow does not expose a structured-data field on CMS items.

What are the tier limitations?

Endpoints (any mix of webhook and platform adapters) count against the overall publishing endpoint cap:

How do you troubleshoot Webflow publishing?

401 Unauthorized on connection test. The API token is wrong, was revoked, or lacks the required scopes. Regenerate it from Site settings → Apps and integrations → API access with CMS read+write and Sites read.

404 for the site or collection ID. The IDs are wrong, or the collection lives on a different site than the one the token authorises. Re-copy both IDs from Webflow.

400 ValidationError: Field 'post-body' does not exist. The collection is missing one of the required field slugs. Add the missing field in Collection settings → Fields with the exact slug shown in Required collection schema.

Item appears in Webflow but not on the live site. Webflow does not auto-publish drafts. Open the Designer, click Publish, or use the admin to publish individual items.

The image is broken. Webflow downloads images from the supplied URL when the item is created. If the URL becomes unreachable, the image field stays empty. Re-publish from CiteFlow to refresh.

Need help?

Copy the Webflow error shown in your CiteFlow dashboard and contact support if the test passes but real publishes fail.