What it does
Wavefront writes each approved article as an item in one Webflow CMS collection. Items go in as drafts by default, or publish to the live site.
You map Wavefront's fields to your collection's fields once, and Wavefront checks the map against the collection before anything is sent. Values that would be empty are left out, so an update never blanks a field an editor filled in.
Before you start
- A Webflow site with a CMS collection for articles
- A rich text field for the body in that collection
How to connect Webflow
- In Wavefront, open Settings → Publishing and choose Add destination. Pick Webflow.
- Choose Connect with Webflow and pick the sites to share, or enter a site API token with CMS read and write and Sites read access.
- Choose Load fields and pick the collection.
- Map the fields: title to Name, slug to Slug and the body to a rich text field. Summary, header image, SEO fields, category and author are optional.
- Choose Test connection. Wavefront checks the site, the collection and that every required field is mapped with a type that fits.
- Save, and choose whether withdrawing deletes the item or only unpublishes it.
What Wavefront sends
- Title, slug and the body as Webflow rich text
- Summary, header image with alt text and credit, SEO title, meta description and canonical URL
- Categories and authors matched to reference or option fields by name; Wavefront never creates them
- Live items are checked until their page loads
- A list of anything Webflow's rich text couldn't keep, so someone can check the item
Good to know
- Scheduling isn't offered: Webflow's API has no publish-at time for an item.
- Webflow's rich text has no tables or code blocks, so tables become one paragraph per row and code becomes plain paragraphs.
- IndexNow can't be used, because Webflow doesn't serve arbitrary files on your site.