Framer Integration: Publish Content Agent Articles to a Framer CMS Collection

Once connected, the ReddGrow content agent publishes articles into a Framer CMS collection, typically a Blog collection, creating and updating items as needed. Framer field IDs aren't shown anywhere in the Framer UI, so instead of mapping fields by hand, ReddGrow matches your collection's Title and Content fields automatically by name.

Publishing deploys your whole Framer project. Framer has no way to push just the CMS change live — every publish promotes the project's current state to production, including any unrelated design edits you have pending in the editor. Finish or discard in-progress edits before connecting, or expect them to go live alongside the content agent's articles.

Requirements

• A Framer project with CMS enabled and an existing collection to publish into
• The collection needs a text field for the title (named Title or Name) and a text field for the body (named Content, Body, Article, or Post). A Meta Description, Description, SEO Description, or Excerpt field is optional and used for meta text
• Owner or Admin access to the Framer project, to generate an API key

The Framer Server API is currently in beta.

Get your credentials

1. Open your project in Framer
2. Press Cmd+K (or Ctrl+K) and search for Open settings, or find Site Settings in the project menu
3. Find the API Keys section under General
4. Click Create API key, name it, e.g. ReddGrow, and copy it immediately — it's shown once

An API key is scoped to the single project it was created in, and acts as the user who created it.

Project URL: copy the URL from your browser's address bar while the project is open in Framer — it looks like https://framer.com/projects/YourSite--aabbccdd1122.

Connect in ReddGrow

1. Go to Settings → Integrations
2. Under Website publishing, find the Framer card and click Connect
3. Fill in the form:
   • Live site URL: your site's full https:// address
   • API key: the key you generated above
   • Project URL: the Framer project URL
   • Collection name: the CMS collection's name, exactly as it appears in Framer, e.g. Blog
   • Path prefix (optional): the URL folder the collection is published under, e.g. /blog. Framer's API doesn't return live URLs, so ReddGrow uses this to build page links
4. Click Connect Framer

ReddGrow resolves the collection name to its internal ID at connect time and stores that, so renaming the collection later in Framer won't break publishing — reconnecting or re-testing repairs it automatically. If another platform is already connected, ReddGrow warns you that connecting Framer will replace it. Only one website can be connected at a time.

Troubleshooting

Connecting fails with "no collection named ..."

The Collection name field must match a collection in the project exactly (case-insensitive). The error message lists every collection name ReddGrow could see — check for typos or a collection created in a different project.

Connecting fails with "collection is missing a Title field / a Content field"

ReddGrow matches fields by name. Rename one of your text fields to Title (or Name) and another to Content (or Body, Article, Post), or add one if the collection doesn't have it yet.

Articles publish to the CMS but don't appear live on the site

This means publish() or deploy() failed after the CMS write succeeded — check Site settings → General → API Keys to confirm the key hasn't been revoked, and that the project doesn't have a blocking issue (e.g. a failed deploy) reported in Framer itself. The connection's last checked error on the integration card carries the underlying message.

An unrelated design change went live at the same time as an article

Expected: Framer publishes and deploys the entire project on every write, not just the CMS change. Finish or discard pending edits in the Framer editor before the content agent's next scheduled publish, or publish content agent output from a project you don't actively design in.

---

Related: see the ReddGrow App guide for how campaigns, drafts, and the platform's automation pipeline fit together.