Connect
Framer
Framer connects with a per-project Server API key rather than OAuth. You create the key inside your Framer project and paste it into Modiva together with the project's URL — one connection maps to exactly one project. Modiva can then read and write managed CMS collections and items, publish and deploy the site, and read locales and code files. The Server API is in open beta, and the key never expires until you revoke it in Framer.
Before you start
- A Framer project.
- A Server API key for that project, created under the project's settings → API Keys.
Step-by-step setup
- 1
Create a Server API key
Open your project in Framer, press Cmd+K (Ctrl+K on Windows) and choose "open settings", then find the API Keys section. Create a key, give it a label like "Modiva", and copy it — treat it like a password, since it can edit CMS content and publish the site.
- 2
Sign in to Modiva
Log in at modiva.ai and open the Dashboard. You need a Modiva account before you can connect any platform — creating one takes a minute and no credit card is required for the free tier.
The Modiva dashboard — your home for connections, posts and analytics. - 3
Open Connections → New connection
In the left sidebar choose Connections, then click New connection. You'll see the full catalogue of platforms grouped by category (Social, Ads and CRM).
The connection picker. Use the search box or category filter to find your platform. - 4
Paste the key and project URL
Click the Framer card. In the inline form paste the API key and the project URL (copy it from your browser while the project is open — it looks like framer.com/projects/Site--abc123). Click Connect.
- 5
You're connected
Modiva opens a Server API session, reads the project's info to validate the key, and shows the connection as Connected. To connect another project, create a key in that project and add a second connection.
Permissions Modiva requests
When you connect Framer, Modiva asks only for the access it needs to run the tools you use. You can revoke it any time from Framer or by disconnecting in Modiva.
- Read the project's info and publish state
- Read & write managed CMS collections and items
- Publish and deploy the site
- Read locales and code files
Troubleshooting & FAQ
Why an API key instead of OAuth?
Framer's Server API authenticates with per-project API keys — there is no OAuth app model. The upside: no app review and nothing to approve; you create a key in your project and connect in under a minute.
Which collections can Modiva write to?
Writes go to managed collections — ones created through the API (Modiva's collections_create tool). Collections built by hand in Framer are listed and readable, but the Server API doesn't allow writing to them.
Does publishing affect my live site?
Yes — the publish tool creates a deployment and, by default, deploys it to your production hostnames. Ask your agent to pass deploy=false if you only want to create the deployment without shipping it.
How do I revoke Modiva's access?
Delete the "Modiva" API key in your Framer project's settings under API Keys, then Disconnect the connection in Modiva.
Need help with Framer?
Fin can answer follow-up questions and walk you through any step.
Framer playbooks
Connected? Put Framer to work with these free growth playbooks.