Publish to Framer

Framer does not expose a public API that lets an outside service create CMS items on any site. That rules out a direct connection of the kind Ghost or Webflow have. What Framer does offer is two doors we already serve: it can import a CMS collection from an RSS feed, and its official Zapier and Make integrations can create CMS items from a webhook. Both are documented below, RSS first because it needs no third tool.

What to know before you start

Pick RSS when the Framer site just needs a blog that stays current. Pick the webhook when you want each article to land the moment it publishes, or when a Zapier or Make workflow already runs the site's content.

Either way the articles are rendered by Framer's own CMS templates. We deliver the content; the Framer designer decides how it looks.

Path 1: feed the Framer CMS from RSS

Every project exposes a keyed RSS feed of its published articles, and the address has one moving part, the share key:

https://searchblueprint.io/api/public/rss?key=<share key>

That key is the token in the project's share link, so copy it from Projects, then Copy share link, and take the part after /share/. Treat the whole feed URL as a password, because anyone holding it can read the feed.

To connect it:

In Framer, open the CMS and add a collection with Framer's RSS plugin as its source.
Paste the feed URL. The plugin maps each item's title, summary, date and full HTML body onto collection fields.
Design the collection's list and detail pages the way you would for any Framer CMS collection.
Re-sync the collection when you want new articles pulled in. Framer polls on its own schedule, so an article that just published can take a while to show.

The feed carries the twenty most recent published articles by default; add &limit=50 for more. Each item's guid is our article id, which is what a feed importer reads to tell an update from a new item.

Path 2: webhook into Zapier or Make

If the site needs articles as they publish, connect the webhook and point it at a Zapier or Make trigger. The trigger receives the article as JSON, with title, slug, HTML, markdown, meta fields and a stable id. The next step in that workflow uses Framer's own Zapier or Make action to create the CMS item.

To set it up:

Create a webhook trigger in Zapier or Make and copy its URL.
In the project's Publishing tab, choose Webhook, paste that URL and set a signing secret.
Add a Framer "create CMS item" action and map title, slug, contentHtml and metaDescription onto the collection's fields.
Send a test publish. The item should appear in the Framer CMS as a draft.

Dedupe on the id field. Deliveries retry up to four times, and the id is the one value that stays the same across every attempt.

What happens after you publish

Articles published through the normal content calendar flow appear in the feed as they go live, or fire the webhook at once. A new CMS item is not on the live site until the Framer project is published again, since Framer pages come from Framer's own publish step. Publish verification cannot see inside Framer, so these paths show as delivered rather than verified.

Limits and usage

Neither path can replace the body of an article that is already in the Framer CMS. A refresh publishes a new item, unless the automation matches on our id and updates in place.
Images stay hosted by us. Framer copies nothing into its asset store on import, so do not delete articles here while a Framer page still shows them.
The RSS feed lists recent articles for syndication. Older articles are not in it.
The share key doubles as the read-only client link for the project. Rotating it changes both.

If something isn't working

Framer says the feed is invalid. Open the feed URL in a browser. If XML renders, the feed is fine and the import is being strict about something optional. Make sure the URL was pasted whole, key and all.

Items import twice. The share key was rotated, so the feed URL changed and Framer treats it as a new source. Keep one feed URL per collection and rotate on purpose.

The webhook fires but no CMS item appears. The Zapier or Make step is mapping a field Framer's collection does not have, or the Framer account connected to the automation has no edit access to that project.