Framer integration
Framer is specified, not connectable yet.
Sync content into Framer CMS managed collections through the Server API, without flattening your design system.
How it works
SearchHandled uses the Framer Server API, launched in 2025, to sync content into a managed collection on your site. Items carry your mapped fields (title, slug, content, images, SEO fields) and render through the collection pages and components you designed in Framer, so the site keeps its design system and we supply the content. Syncs are idempotent, keyed on stable slugs, so re-running a sync updates items rather than duplicating them.
Publishing in Framer is site-level: synced items exist in the CMS, and they appear on the live site when the site is published. There is no per-item publish, so our flow is sync, review, then a site publish that you trigger or approve. Managed collections have plan-based limits, 1,000 items on Pro and 10,000 on Scale, plus a 30-field cap, and we check capacity before syncing rather than failing at the wall.
Best forTeams that built their site in Framer and want CMS content flowing in without giving up how the site looks.
Setup, step by step
- Connect SearchHandled to your Framer site through the Server API and choose or create the managed collection for your content.
- Map collection fields to SearchHandled content fields, staying inside Framer's 30-field limit.
- Run the connection check, which verifies write access and reports current collection capacity against your plan's cap.
- Sync a test item and confirm it renders correctly through your collection page design.
- Decide how site publishes happen: triggered on your approval, or on a schedule you set.
Best practices
Understand managed collection ownership
Managed collections are owned by the integration that writes them, and managed items are not freely editable by users in the Framer CMS UI. Plan for edits to flow through SearchHandled, with specific fields unlocked for in-Framer editing where you need them.
Design collection pages before ramping volume
Since Framer renders CMS items through your collection page design, get one synced item looking right first. Every subsequent item inherits that work.
Leave headroom under the item cap
Collections hard-cap at 1,000 items on Pro and 10,000 on Scale. Keep a margin for growth, and archive or consolidate old items before the cap becomes an emergency.
Batch content, then publish the site
Because publishing is site-level, publishing after every single item churns your whole site. A rhythm of syncing a batch and publishing once is calmer and matches how Framer works.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Managed items are not editable in the CMS UI
Write access through the Server API is scoped to plugin-managed collections, and items in a managed collection cannot be edited by users in the normal Framer CMS interface, which surprises teams expecting to tweak content in place.
How we handle itWe document the ownership model plainly at setup and unlock specific fields for in-Framer editing selectively where your workflow needs it.
framer.com/developers
Duplicate items from a sync bug
A recent Framer bug caused synced items to be duplicated, fixed in Plugins 3.9, leaving affected collections with double entries.
How we handle itOur sync is idempotent, keyed on stable slugs, and a dedupe pass catches and removes duplicates even if an upstream bug reintroduces them.
framer.com/updates
Hard collection caps break imports
Collections stop accepting items at the plan limit, so imports and syncs fail outright once a collection is full.
How we handle itWe run a capacity pre-check before every sync and warn you as the collection approaches its cap, so the limit is a planning conversation instead of a failed delivery.
framerhub.io, brixtemplates.com
Questions teams ask
- Can individual posts be published one at a time?
No, Framer publishing applies to the whole site, not per item. Synced items sit in the CMS until the next site publish. We work with that honestly: sync first, review, then a site publish you control.
- Why can't my team edit synced posts inside Framer?
Framer's managed collections are owned by the writing integration by design, so managed items are locked in the CMS UI. We can unlock selected fields for in-Framer editing, and everything else edits through SearchHandled refreshes.
- How new is this API, and is that a risk?
The Server API launched in 2025, so it is newer than most CMS APIs we integrate with, and Framer is still evolving it. We track their updates closely, and our idempotent sync plus dedupe pass exists precisely to absorb upstream changes safely.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Framer matters moves it up the rollout.