Webflow

The Webflow integration publishes Content Agent drafts directly into a Webflow CMS collection, so an approved draft becomes a staged CMS item, and then a live page, without copy-pasting into the Designer.

​

Connect your Webflow account

1. Click Settings at the bottom of the left rail, then open CMS Integrations under Project settings.
2. On the Webflow card, click connect. You’ll be redirected to Webflow’s authorization screen.
3. Approve the requested access. Promptwatch asks for read access to your sites and pages, and read/write access to CMS items and assets, which is what publishing needs and nothing more.
4. You’re redirected back to Promptwatch to finish configuration.

You can also start from the Webflow side: installing the Promptwatch app from Webflow’s marketplace walks you through picking the Promptwatch organization and project to connect, then runs the same authorization.

​

Configure the connection

After authorizing, a three-step wizard opens:

​

Site

Choose which Webflow site to publish to. If your account has exactly one site, it’s selected automatically.

​

Collection

Pick the CMS collection where documents should land, usually your blog or articles collection. If the collection doesn’t exist yet, create it in Webflow first and hit the refresh button next to the dropdown.

​

Field mapping

Every field in your collection gets a source. When you pick the collection, Promptwatch suggests one per field: rows marked Matched automatically were matched by name, and an AI suggestion comes with its reasoning and a confidence score. Each row also shows the help text you wrote for that field in Webflow. Check the suggestions and change any you disagree with. A source can be:

• A Promptwatch field: title (H1), meta title, description, content, featured image, publish date, or author name, title, and image. Map Meta title to your SEO title field; it falls back to the H1 when empty. One source field can fill more than one collection field.
• AI: generate per document: the AI writes a value for that field from each document, useful for fields Promptwatch has no source for, like a category or a summary line.
• Fixed value: the same value on every item.
• Leave empty.

Title and Content must be mapped, and a required field can’t be left empty: rows that still need attention are marked Needs a look. When a connection has AI-generated fields, Publish as CMS draft and Update CMS draft first open Review AI-filled fields before publishing, where you check or edit each value. If the Content Agent is set to publish live and the AI isn’t confident about a required field, it stops at a CMS draft instead, and the publication card asks you to Review and publish. Save the configuration and the connection is ready.

​

Push a draft

Open a draft in the content editor and find the publication card. Publish as CMS draft creates the item in your Webflow collection as a staged draft: it exists in the CMS but is not live. That staging step is deliberate, so your team can review the item in Webflow’s own editor, adjust styling, or slot it into a design before anything goes public. If you edit the document in Promptwatch afterwards, click Update CMS draft to update the staged item.

​

Publish live

When the item is ready, click Publish live on the publication card. Webflow publishes that single item, so your site is untouched apart from the new page. This is a real difference from Framer, where going live redeploys the whole site.

​

After you publish

The publication card shows the publish status for each document and, once live, a link to the published URL. If your Webflow authorization ever expires, the connection is flagged on the CMS Integrations page and a reconnect keeps your site, collection, and field mapping intact. To see how published pages perform in AI answers afterwards, see Publishing and tracking.