We load the collection schema
The load fields button pulls the real field names from your collection. We do not guess them, because a wrong field name is the single most common reason a publish is rejected.
Integration
Webflow
Webflow collections have no fixed schema — every site defines its own fields. So setup starts by pulling your collection schema and mapping what goes where.
What we need from you
- An API token from Site settings → Apps and integrations → API access.
- The Collection ID of the target collection (CMS → collection → Settings).
- Your public domain, so we can build a link to the published article.
What lands on the destination
- Item name and slug
- Article body as Rich text, with H2/H3 structure
- Summary (meta description) in the field you mapped
- Featured image, which Webflow pulls onto its own CDN
- Category, if you mapped a text field for it
How it works
The publishing flow, step by step
We map what goes where
Body, summary, featured image and optionally a category. If the collection came from the Webflow blog template, the defaults already match.
Draft or live
Draft keeps the item inside the CMS for review. Live means the item goes onto the site at the scheduled time.
Limits
What this integration does not do
It's on the page on purpose. Better seen now than after the first publish.
- We do not upload into the Webflow asset library. We hand over a URL and Webflow fetches the image itself, which for most sites is the same result with fewer moving parts.
- Reference and multi-reference fields are not populated. The category travels as plain text.
- If an item with the same slug already exists, Webflow rejects the write and the panel says so immediately.
FAQ
Common questions — Webflow
Can I change the token without deleting the integration?
Yes. The token is replaced in place and the delivery history stays. You never have to delete and recreate the integration.
What if my collection has no summary field?
Leave that mapping empty. We only send fields that exist, so the meta description then lives in our panel and on the hosted blog.
Other integrations
One site can publish to several destinations at once
WordPress Publishing through the official REST API with an application password. No plugin. Ghost Admin API with signed tokens, images into the Ghost library, tags. GitHub Markdown into a static site repo — Astro, Hugo, Next and friends. Webhook and public API Signed JSON to your endpoint, or pull the content yourself through the API. Custom integration Your system is not on the list and you have nobody to write the code? We build the integration; you change nothing.
Next step
Ready for organic growth?
Connect any site — services, webshop or blog. The plan builds itself, articles are written and published on schedule, and the first one is free.