The Webflow connection writes generated articles into a CMS collection on your Webflow site. Your Webflow templates then render them like any other CMS item — the connection delivers structured content into the collection you point it at.
New connections default to draft items, so posts wait in Webflow for your publish action until you switch the connection to publish live.
What to know before you start
Connect it when the project's blog lives on Webflow. One design prerequisite: a CMS collection for blog posts must already exist. The connection fills collections — it doesn't design them.
Connect Webflow
To connect Webflow:
- In Webflow, create a site API token (
Site settings→Apps & integrations). - Find your blog collection ID (
CMS→ your collection → settings). - In your project's
Integrationstab, choose Webflow, paste the token and collection ID, and send a test publish. - Check the item in Webflow's CMS panel, then publish the site — Webflow shows CMS changes on the live site only after a site publish.
What happens after you publish
Articles land as collection items with the fields mapped — title, body, slug, and metadata into the fields your collection provides. The publish verifier then checks the public URL. Note that it can only pass after you publish the Webflow site itself.
Limits and usage
- The token is site-scoped: one connection per Webflow site.
- Field mapping follows common collection field names. A heavily customized collection may leave extra fields empty for you to fill in Webflow.
- Webflow's own CMS item limits apply — a plan at its item cap refuses new posts, and the connection surfaces that error rather than hiding it.
If something isn't working
Items appear but the live site shows nothing. You haven't published the Webflow site since the items arrived. Publish in Webflow — the verifier flips to live on its next check.
You get authentication errors. Site tokens expire when regenerated — paste the current one. Workspace-level tokens don't work; it must be the site API token.
Content lands in the wrong collection. The collection ID points elsewhere. Copy it from the collection's settings screen, not from the page URL.