Publishing integration
Publish to Webflow
Creates a live CMS item via the Webflow Data API v2, field-mapped to your collection's slugs.
How it works
Publishes directly into a CMS Collection via Webflow's Data API v2, live rather than staged, so there's nothing to manually publish afterward.
Before you start
- A Webflow site on a CMS or Business plan (the Data API needs CMS access)
- At least one CMS Collection already created to hold blog posts
- An API token generated from Webflow's Data API settings
Setup
Three steps to connect
Step 1
Get your api token
Site settings -> Apps & integrations -> API access -> generate a Site API token (or a Data API OAuth token).
Step 2
Enter your site details
- Collection ID *Site settings -> Apps & integrations -> API access, or open the CMS collection in the Designer -- the ID is in its settings panel.
- Published site URL (optional)Used only to build a best-guess post URL; skip if your blog isn't at the site root.
- Field map (JSON, optional)Maps our post fields to your collection's field slugs. Defaults match Webflow's common blog template.
Step 3
Connect and publish
Once connected, approved posts publish straight to Webflow automatically. No export, no import, no copy-pasting into a CMS. Setup runs from your own client portal, so credentials for Webflow stay with you; the agency never has to hold or request them separately.
Troubleshooting
If something doesn’t connect
Connection test fails with "Collection ID is required"
The Collection ID isn't the Collection's display name. Open the collection in Webflow's Designer or CMS panel; the ID is in the URL or the collection settings panel.
Posts publish but fields look empty on the live page
Field slugs are project-specific. If your collection doesn't use Webflow's common blog-template slugs (name/slug/post-body/post-summary), map them explicitly in the field mapping during setup.
Frequently asked questions
Yes. It fills your existing Collection fields, the same ones your Webflow templates already render, so styling carries over automatically.
You map them once during setup, a small JSON field-to-slug mapping. After that, every post uses it automatically.
Body content publishes as Webflow Rich Text. Standard formatting (headings, lists, links, images) carries over; highly custom embeds don't.
Credentials are encrypted at rest and only ever used server-side to publish. Nobody, including us, can view them again once saved.
Nothing changes on Webflow itself. Everything already published stays exactly as it is. New posts just stop syncing until it's reconnected.
Still have questions? Talk to our team.
Ready to connect Webflow?
Book a call and we'll get your site's publishing integration set up together.