Skip to main content
The Framer integration publishes Content Agent drafts into a Framer CMS collection. The flow mirrors Webflow: connect, pick a collection, map fields, push drafts, publish live. The differences come from how Framer itself works, and they matter, so they’re called out below.

​
Connect your Framer project

Framer connections use an API key instead of OAuth, and each connection is bound to a single Framer project:
  1. Open Settings in the left rail, then CMS Integrations under Project settings.
  2. On the Framer card, click connect.
  3. Paste your project URL: open the project in Framer and copy the URL from the address bar (it looks like https://framer.com/projects/your-site--abc123...).
  4. Paste an API key from that project’s settings in Framer. Once the project URL is filled in, the form shows a direct link to the settings page where API keys live.
  5. Click Connect with Framer. Promptwatch validates the key against Framer before saving, so a typo fails immediately instead of at publish time.
The Promptwatch Connect your Framer site dialog with the Project URL and API key fields.

​
Configure the connection

Because the connection is already bound to one Framer project, there is no site-picker step. The wizard goes straight to:
  • Collection: pick the CMS collection where documents should land, usually your blog. Create it in Framer first if it doesn’t exist, then refresh the list.
  • Field mapping: Promptwatch suggests a source for every collection field, matched by name or as an AI suggestion with reasoning and confidence. A source is a document field (title (H1), meta title, description, content, featured image, publish date, author fields), AI: generate per document, a Fixed value, or Leave empty. Title and Content are required, and a required field can’t be left empty. Map Meta title to your SEO title field; it falls back to the H1 when empty. With AI-generated fields, you review their values before each CMS draft goes out. The Webflow guide describes the same mapping step in more detail.

​
Push a draft

From a draft’s publication card in the content editor, Publish as CMS draft creates the item in your Framer collection as a CMS draft, and Update CMS draft overwrites it after edits. It is staged, not live, so you can review it in Framer first. Updating the CMS draft never rebuilds your site, so you can push revisions freely.

​
Publish live: read this part

Here is the real difference from Webflow: Framer has no per-item publish. Making a CMS item live requires rebuilding and deploying the entire site, the same as pressing Publish inside Framer. Two consequences:
  • Other unpublished changes go live too. If someone on your team has unpublished edits sitting in the Framer editor, publishing a document from Promptwatch deploys those as well.
  • Promptwatch asks for confirmation. Before publishing live, a dialog spells out that the whole site will rebuild and deploy, so nobody triggers a site-wide deploy thinking it’s a single-page action.
If your team keeps work-in-progress in the Framer editor, coordinate publish timing, or let drafts accumulate as staged CMS items and publish them in one intentional deploy.

​
After you publish

The publication card shows the publish status and, once the item is live, the published URL. If the API key is revoked or expires, the connection is flagged on the CMS Integrations page; reconnecting with a fresh key keeps your collection and field mapping. For measuring how the published page performs in AI answers, see Publishing and tracking.