Integration guide

Framer publishing integration

Connect a Framer CMS project with API credentials so approved articles can be pushed into the right collection.

Open Dashboard All Integrations

API key: Auth
Draft/live: Modes
Queue: Runtime

Publishing integrationAPI key

Connect a Framer CMS project with API credentials so approved articles can be pushed into the right collection.

Summary

Auth: API key
Modes: Draft/live
Runtime: Queue

Open Dashboard All integrations

Connecting Framer with api key

Connect a Framer CMS project with API credentials so approved articles can be pushed into the right collection. The dashboard walks through the api key handshake and verifies the CMS collection before anything is queued, so the CMS collection approved content will land on is confirmed up front rather than discovered on the first failed publish.

Choosing the CMS collection

Once Framer is connected, the CMS collection is selected per business rather than set globally. Agencies running several Framer properties can keep each one pointed at its own CMS collection without re-authenticating between publishes.

What reaches Framer

Approved content keeps its title, slug, excerpt, body, metadata, CMS collection, and scheduling together on the way across, so what appears in Framer matches what was reviewed instead of a stripped-down copy that needs fixing after the fact.

Credentials, failures, and revocation

Framer credentials stay server-side and scoped to the selected business, never reaching the browser. Publishing runs only through the configured production adapter, and if Framer rejects a request the item stays queued with the provider error attached so the fix happens once instead of the same post being retried blindly.

Next step

Move from reading to the working SEO system.

Open the audit, onboarding, or publishing workflow and keep the next action tied to a real business profile.