How to connect Framer to Orchly
Connect a Framer project with an API key so agents can publish to your CMS collections.
To connect Framer to Orchly, copy your Framer project URL, generate an API key in Framer’s site settings, and enter both in Settings → Integrations → Framer. Agents can then publish articles into your Framer CMS collections and update existing items.
How do I get a Framer API key?
- Open your project in Framer.
- Copy the URL from your browser’s address bar. It looks like
https://framer.com/projects/…. This is your Project URL. - Go to Site Settings → General → API Keys and generate a key.
- Copy the key.
Each Framer connection points at one project, so there’s no site to pick later. The project URL decides where content goes.
How do I connect Framer?
- In Orchly, go to Settings → Integrations and click Configure on Framer.
- Paste your project link into Project URL.
- Paste the key into Framer API Key.
- Click Connect Framer.
The badge changes to Connected, and the drawer’s Details section shows the project.
To swap the key later, open the drawer, enter a new key and click Save changes. Leave the key field blank to keep the saved one.
How do I choose which collection to publish to?
Framer’s CMS is organized into collections, each with its own fields. Orchly maps article fields to yours automatically when it can, but it’s worth checking:
- Open the Framer drawer.
- Under Content mappings, click Map a collection.
- Pick the collection, such as Blog or Resources, and choose what fills each field: title, body, slug, excerpt and the rest.
Without a mapping, articles publish as a single body. See publishing agent output.
What can agents do in Framer?
- Publish CMS items, as drafts or live.
- Update existing items, for example refreshing a case study with new numbers.
- Add several items at once, like “Add these three articles to the Resources collection”.
Framer shows up under Can post to in an agent’s Tools & data, so you can turn publishing on per chat or per agent. Orchly asks before publishing and defaults to a draft. See publishing agent output.
When an agent publishes live, Orchly publishes and deploys your Framer project so the new item goes live. Any other unpublished edits in that project go live with it. If your team edits the site often, stick to drafts and publish from Framer yourself.
What can’t it do?
Framer’s API updates CMS collection items only. It doesn’t expose per-page SEO settings, so Orchly can’t change page titles, meta descriptions, schema or redirects on a Framer site. When the Site Health Agent finds that kind of issue, you’ll need to fix it in Framer.
Troubleshooting
| Problem | What to check |
|---|---|
| Can’t connect | Check the Project URL is the full link from the address bar, and that the key is from the same project. |
| Articles land as one big body | Map a collection under Content mappings. |
| Item saved but not on the site | It was saved as a draft. Publish it in Framer, or ask the agent to publish live. |
To remove Framer, open its drawer and click Disconnect.