What the connection does
The connection holds a Webflow site API token, the id of the collection to create items in, and whether an item should be published live or left as a draft. Publishing an approved article creates an item; publishing it again patches the item it created.
Five fields are written: `name` from the title, `slug` from the slug you edited, `post-body` from the article rendered as HTML for a rich-text field, `post-summary` from the meta description, and `main-image` from the cover. A blog collection generated from Webflow's own template already has those field slugs. A collection you designed yourself may need them renamed to match, because PrismDraft never creates or alters a collection's fields.
Section images are referenced from inside the body HTML with the alt text you approved, served from PrismDraft's storage rather than uploaded into Webflow's asset manager.
- Needs: a Webflow site API token and the collection id.
- Writes: `name`, `slug`, `post-body`, `post-summary`, `main-image`.
- Never creates or changes collection fields, and never edits your pages or templates.
From your website to Webflow
- 01
Your website becomes a project
One address. PrismDraft reads your pages and drafts the project, the audience, the brand voice and the image style, which you edit before saving.
- 02
A topic with a keyword and an intent
Suggestions arrive on a planning board, each with a working title, a primary keyword, a search intent and a cluster. A keyword the project covers is not proposed twice.
- 03
An outline you approve
A heading per section with its job, its keywords and a target length. Free to generate and free to change, and the thing the draft is written against.
- 04
The run, priced first
About 7 credits for 1,200 words and three images, shown before you start. Each section is written against its heading, with an image prompted from the paragraphs beside it and alt text.
- 05
Approve, then publish to Webflow
Review with versions and comments, edit by hand or with AI, then approve. Publishing is only available from the approved state.
What arrives in the collection item
Five fields, and nothing else. A field not listed is not written.
| Article field | Collection field | Notes |
|---|---|---|
| Title | name | As approved |
| Slug | slug | Editable before approval |
| Body | post-body | HTML for a rich-text field |
| Meta description | post-summary | Short enough for a card |
| Cover image | main-image | Referenced by URL |
| Section images | inside post-body | Referenced by URL, with alt text |
| Live or draft | isDraft | Set on the connection, not per article |
| Other fields | — | Left untouched, including any you added |
Setting it up
In Webflow, create a site API token with permission to write CMS items, and copy the collection id of your blog collection. In PrismDraft, open the project's integrations, choose Webflow, and paste both. Decide whether items should go live or wait as drafts.
Publish one article and open the item in the CMS. Check that `post-body` kept its headings, that `main-image` is filled, and that nothing your template needs is empty. If a field is missing from the collection, rename it rather than asking PrismDraft to write a different one — five fixed field slugs is what keeps this connector boring, and boring is what you want from a publish step.
Questions
Which collection do items go into?
The one whose id you give when you create the connection. PrismDraft creates items there and never creates or alters the collection's fields.
What if my collection uses different field names?
Rename them to `name`, `slug`, `post-body`, `post-summary` and `main-image`, or create a collection from Webflow's blog template, which already uses those slugs.
Does it publish the site after creating the item?
The item is created live or as a draft according to the connection. Whether your site needs a publish in Webflow for the item to appear depends on your setup; CMS items on a published site normally appear immediately.
Are images uploaded to Webflow?
No. They are hosted by PrismDraft and referenced by URL, both for the main image and for the images inside the body.
Can I keep a project per Webflow site?
Yes. A connection belongs to a project, so each site gets its own token, its own collection and its own brand voice.
Is there a webhook instead?
Yes. A signed outbound webhook posts the article to a URL you control with a signature you verify, which is the route to take if you want to transform the payload before it reaches Webflow.