Connect Webflow & map fields

What this is: How to connect Webflow, choose which collections to publish into, map platform content fields to your Webflow CMS fields, and what happens when you publish.

Prerequisite: You need access to the Webflow site you want to publish to, and permission to authorize apps for it.

Webflow is one of two CMS options (the other is WordPress). Connecting a CMS is required to publish, and it unlocks the Website overview area.

Before you start

Get these in place in Webflow first. The platform maps onto your existing structure; it never creates collections or fields for you.

• A site with CMS collections. Publishing writes items into a collection that already exists. If your site has no collections, create one in the Webflow Designer first.
• The fields you want us to fill. Webflow's built-in SEO and Open Graph settings cannot be written through its API, so anything you want populated needs a real field on the collection. See SEO and Open Graph fields below.
• Any authors or categories as CMS items. If your Author or Categories field is a Reference or Option field, we match by name against what already exists. No match means that one field is skipped.
• Permission to authorize apps for the site, and a Webflow plan that includes the CMS.

Connect

1. Go to Settings → Integrations.
2. Set the CMS to Webflow.
3. Click Connect Webflow.
4. A Webflow window opens (OAuth). Authorize the app.
5. Return to the app. You'll see a Webflow connected confirmation.

What you're granting. The authorization asks for read access to your sites and pages, and read plus write access to CMS items. That is the minimum needed to list your sites and collections, read your existing content for the website index, and create draft items. We never publish your site live and never touch your Designer layout.

Coming from the Webflow Marketplace? The Install link works even if you don't have an account yet. It remembers where you were heading, sends you to log in or sign up, then resumes the Webflow authorization automatically once you have a workspace.

If the connection fails, you'll get a "Connection failed" notification and stay on the Integrations page. Nothing is stored, so just click Connect Webflow again. The connection card is always the source of truth for whether you're connected.

Pick your site

Once connected, a Site dropdown lists every site covered by the authorization (a Webflow workspace often has several). Pick one and its collections load automatically.

Changing the site later clears the loaded collections, so you'll re-pick collections for each content type.

Configure each content type

Each content type gets its own collection and its own field mapping, so articles and glossary terms can live in different collections with different fields.

Pick a type from the chips, then choose its collection. A tick on a chip means that type is already configured. If two types share a structure, use Copy collection + fields from to clone a configured type's setup and adjust from there.

Content type	Publishes to Webflow today
Article	Yes
Glossary term	Yes
Whitepaper, eBook, Datasheet	No, PDF deliverables
Benchmark report, Trend report, State-of report	No, PDF deliverables

The PDF types can still be configured. The mapping is saved and will be used once those types support CMS publishing. Only types with a collection actually chosen are stored when you save.

Map your fields

Map each platform field to a field in your Webflow collection using the mapping grid. Sensible defaults are pre-filled, and the dropdown shows each Webflow field's name, slug and type, so you can tell a Rich Text field from a Reference field before you pick it.

Platform field	Default Webflow slug	Notes
Title	name	Required
Slug	slug	Required
Body (article sections)	post-body	The H2 sections of the article
Meta title (SEO)	meta-title	Needs a custom field, see below
Meta description (SEO)	meta-description	Needs a custom field, see below
OG title	og-title	Needs a custom field, see below
OG description	og-description	Needs a custom field, see below
Introduction	summary	Rich content, see appending below
FAQs	faqs	Rich content
Conclusion	conclusion	Rich content
References / Sources	references	Rich content
Author	author-name	Text, Reference or Option field
Featured image	main-image	Image field
OG image	og-image	Image field
Focus keyword	focus-keyword	Plain text
Canonical URL	canonical-url	Plain text
Categories	categories	Text, Reference or Option field

Title and Slug are required. If you leave either unmapped we fall back to Webflow's own name and slug fields, because Webflow rejects any item without them.

Article content can be split or combined

Introduction, Body, FAQs, Conclusion and References are five separate pieces of rich content. You choose how they land:

• Map them to separate Rich Text fields to keep them apart in your template.
• Map several to the same Rich Text field to combine them. They are appended in reading order (Introduction, Body, FAQs, Conclusion, References), never overwritten.
• Leave one unmapped and it is appended into the Body field instead. Nothing is silently lost.

All five use the same Markdown to HTML conversion as the WordPress body, so headings, tables, links, bold and lists survive into whichever field they land in.

If your workspace has the TL;DR block enabled, it is prepended to the Introduction so it leads the article, matching the WordPress order.

Author and Categories

These two can map onto a plain-text field or a Reference / MultiReference / Option field.

• Text field: we write the author name or a comma-separated category list straight in.
• Reference or Option field: we match your author or category name against the items in the referenced collection (or the option list) and send the matching id.

If there's no match, that one field is skipped and the rest of the article still publishes. So create the matching author or category item in Webflow before you publish.

In the Extras stage, the Author control adapts to what you mapped: a Reference field gives you a dropdown of real Webflow authors, a text field gives you a free-text byline.

Images

Featured image and OG image must map to Webflow Image fields. We send the image URL and use the article title as alt text, and Webflow fetches the file itself. There is no upload step and no file size handling on your side.

SEO and Open Graph fields

Webflow's built-in SEO and Open Graph settings cannot be set through its API. To populate them:

1. In the Webflow Designer, add Plain Text / Image fields to the collection (for example "Meta Title", "Meta Description", "OG Image").
2. Bind the collection page's SEO and OG settings to those fields.
3. Come back here and map our Meta title, Meta description, OG title, OG description and OG image onto them.

We check field types before sending

When you publish, we read the collection's schema and route each value to a field that can accept it. A mismatch (rich text aimed at a Reference field, a text value aimed at an Image field) is skipped and logged rather than failing the whole item, so one bad mapping never blocks the article. The exception is Title and Slug, which Webflow always requires.

When you're done, click Save Webflow settings. A "Webflow settings saved" confirmation appears. If the save fails, the reason is shown instead, just above the buttons and as a notification.

What happens when you publish

Publishing happens from the Extras stage of a content project (see Extras & publishing). Autopilot publishes exactly the same way on its schedule.

1. We create the item in your mapped collection as a draft, never archived, never live.
2. The slug comes from the article's slug, or is derived from the title if there isn't one. If Webflow rejects it as a duplicate, we retry once with a short suffix rather than failing.
3. The project moves to Published and records the Webflow item id.
4. Open in Webflow takes you straight to that item in the Designer's CMS editor. Webflow drafts have no public URL, so this is a Designer link, not a live page.
5. You review the draft and publish it live from Webflow yourself.

Publishing runs in the background. You can leave the page; the status updates when it finishes.

If it fails, the project returns to In progress so you can fix the mapping and retry. Start with the field mapping: a rejection almost always means one mapped field will not accept what was sent. If you cannot spot it, contact support with the article title and the time you tried, and we can tell you which field Webflow rejected.

If you try to publish a content type that has no collection configured, you'll be told which type is missing rather than having it silently fall back to another CMS.

Import your existing site

With Webflow connected, the website index is built from the CMS API instead of a crawler. Click Import from Webflow and we pull every collection item and every static page directly.

• Draft and archived items are skipped. Only live content is imported.
• Every collection is indexed for internal linking and research.
• The collection you mapped to Article is the one treated as your articles, so those become part of your content library.
• For recurring audits, a Blog collection dropdown replaces the URL-pattern box, so you pick the collection rather than guessing a path.

Disconnect

Use the Disconnect button. You'll be asked to confirm, because publishing falls back to WordPress until you reconnect. Once done you'll get a "Webflow disconnected" confirmation.

Your site mapping and field mappings are kept, so reconnecting later does not mean redoing the setup.

Troubleshooting

What you see	What it means
"Webflow connection is invalid or expired"	The authorization was revoked or expired in Webflow. Reconnect from Settings → Integrations.
"Webflow rate limit reached"	Too many requests in a short window. Wait a minute and retry.
"Your CMS rejected the article (field validation)"	A mapped field will not accept what we sent. Re-check each mapped field's type in the Webflow Designer, starting with any Option, Reference or Number field. If it still fails, contact support with the article title.
"No Webflow collection is configured for ARTICLE"	That content type has no collection chosen. Pick one under its chip and save.
No sites or no collections in the dropdown	The authorization doesn't cover that site, or the site has no CMS collections. Check the Webflow workspace and plan.
The author or category is empty on the draft	The name didn't match any item in the referenced collection. Create it in Webflow, then republish.
Meta title and description are empty	Webflow's built-in SEO fields can't be written through the API. Add custom fields and bind them, as described above.