Browse guides

Connect Webflow

Publish articles into a Webflow CMS collection with a site API token and the collection’s ID.

Before you start

  • A plan that includes CMS publishing — compare plans on the pricing page. How many connections you can have also depends on your plan.

  • A Webflow site with a CMS collection for blog posts, and permission to create API tokens for it.

Steps

  1. Step 1: Generate an API token

    In Webflow, open Site settings → Apps & integrations → API access and choose Generate API token. The token needs the cms:write scope.

  2. Step 2: Find the collection ID

    In the Designer, open CMS, select the collection you publish into and open its settings. Copy the Collection ID.

  3. Step 3: Open the project’s integrations

    Go to Projects & integrations in the sidebar, open the project you publish from, and choose Integrations. Choose Connect a CMS to open Connect a destination.

  4. Step 4: Enter the Webflow details

    Set Platform to Webflow. Give it a Connection name you will recognise in the publish panel, for example “Company blog”.

    • API token — the token you generated.
    • CMS collection ID — the ID you copied.

    Choose Connect. We check the credentials before saving and store them encrypted. They are never shown again or sent to your browser.

  5. Step 5: Test it and make it the default

    The connection appears under Publishing destinations, with what it supports (scheduling, drafts, featured image, tags). Choose Test at any time to check the credentials still work.

    If the project has more than one destination, choose Make default on the one the publish panel should preselect. Disconnect deletes the stored credentials; posts already published stay where they are and your publishing history is kept.

What you’ll see

Webflow is listed under Publishing destinations. Webflow has no scheduling of its own, so a scheduled article is held by us and submitted at the time you chose.

Troubleshooting

The token is refused

Generate a new token with the cms:write scope for the same site as the collection, and check you pasted it whole.

Articles land in the wrong collection, or are refused

Check the CMS collection ID belongs to the collection you meant and to the same site as the token. Disconnect and connect again with the right ID.

  • Publish an article to your CMS

    Send the saved version of an article to a connected site as a draft, immediately, or at a scheduled time — and follow every attempt in the publishing history.

  • Connect WordPress

    Connect a self-hosted or WordPress.com site with an application password, so articles can be sent as drafts, published or scheduled.

  • Connect Ghost

    Connect a Ghost site with an Admin API key from a custom integration.