Framer Playbook
How to Sync Content Into Framer CMS and Publish With AI Agents
Your Framer site's content rarely starts in Framer — it starts in Notion, Airtable or a spreadsheet, and someone re-types it into the CMS before pressing Publish. The Server API removes both steps: an agent writes the collection and ships the deploy. Here's the loop.
What top site teams do
The habits behind Framer sites whose CMS never drifts from the source of truth.
Treat the CMS as a build artifact
Keep content authoring in the tool the team already uses and let an agent regenerate the Framer collection from it on every sync.
Why it works: Content that's copied by hand drifts within a week; content that's synced can't.
Define the schema once, in code
Create a managed collection with explicit fields (title, slug, body, image) and reuse it for every sync instead of hand-building collections per page.
Why it works: A stable schema is what lets an agent map source fields to CMS fields reliably.
Make publish the last pipeline step
After items land, create a deployment and ship it to production in the same run.
Why it works: A sync that stops short of publishing still needs a human in the loop — the win is ending the run with the site live.
How this plays out in practice
Generalized examples of the kinds of teams running this play.
Kept the blog in Notion; an agent synced ready posts into a managed Framer collection and published — the site updated minutes after an editor flipped a status.
Connected each client's Framer project with its own scoped API key, so content updates ran per client without shared logins or opening the editor.
The examples above are generalized, illustrative descriptions of common approaches across the industry. They are not based on, attributed to, or affiliated with any specific company or individual, and are provided for educational purposes only.
Steal these templates
Copy-paste starting points. Swap the brackets for your own topic and ship.
ON SYNC: read source rows (Notion / Airtable / Sheets, already in Modiva)
ensure managed collection exists → collections_create with fields
items_add: one item per row ({id, slug, fieldData})
publish_site → deployment shipped to production
WEEKLY: items_list vs source → remove orphans with items_removeDo it with Modiva
Here’s how to run this play for real — connect once, then publish, schedule and automate across every platform from one place.
- 1
Connect Framer to Modiva
Sign in at modiva.ai, open Connections → New connection and pick Framer. You authorize on Framer's own screen — Modiva stores only a scoped, encrypted token, never your password. The free tier connects your first three accounts at no cost.
💡 Connecting once makes Framer available to every REST API call and MCP key in your workspace — you never wire up OAuth again.
- 2
Create the managed collection
Use the collections_create tool to make an API-writable collection with explicit fields. Only managed (API-created) collections accept writes, so this one becomes the sync target — hand-built collections stay readable but untouched.
💡 Stable field ids (title, slug, body) make the agent's source-to-CMS mapping deterministic.
- 3
Sync items and publish
Have an MCP-connected agent read the content source, upsert items into the collection with items_add, then call publish_site — Framer creates a deployment and ships it to your production hostnames in the same run.
💡 Publishing ships the live site. Ask the agent to pass deploy=false while you're testing the mapping.
- 4
Let an AI agent run the busywork
Create an MCP key and point your AI assistant (Claude, Cursor, or any MCP client) at Modiva. The agent can draft variations, schedule posts, pull engagement and reply to comments through typed tools — across every connected platform at once.
💡 Describe the playbook to your agent in plain language ('repurpose this video into 5 platform-native posts and queue them') and let it call the tools.
FAQ
How does Framer authentication work?
With a per-project Server API key — no OAuth. Create it in the project's settings (Cmd+K → open settings → API Keys) and paste it into Modiva with the project URL; the key is encrypted at rest and revocable from Framer at any time.
Can Modiva write to collections I built by hand?
No — the Server API limits writes to managed collections (ones created through the API). Hand-built collections are listed and readable. Create a managed collection with collections_create and point the sync at it.
Will publishing overwrite manual changes?
Publishing ships whatever the project currently contains — the same as pressing Publish in Framer. The sync only touches the managed collection's items, so canvas and page edits ride along unchanged.