Framer

Ownership and availability#

You own the Framer project and project-scoped Server API key. Obelo encrypts the key and uses it only for that project.

Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.

Before you connect#

• Edit access to the target Framer project
• A CMS Collection whose fields match the content you want to sync
• A project-scoped Server API key from Site Settings → General

Connect an existing account#

1. Open the provider in Settings → Integrations for the intended website.
2. Copy the Framer project URL
3. Generate a Server API key in the project's General settings
4. Submit both values so Obelo can validate and discover CMS Collections

If you need a new resource#

1. Create a Framer project and add a CMS Collection
2. Define title, slug, content, image, and status fields as needed
3. Generate and securely copy the project-scoped Server API key

Permissions to check#

• The Server API key acts with the access of its creator and is bound to one project
• Rotate the key in Framer if the project owner or access policy changes

Verify and troubleshoot#

Return with the project URL and newly generated Server API key.

No Framer CMS Collections were returned. Confirm the project URL, key, and Collection exist, then sync again.

Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.

Disconnect or change access#

Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.