Integration guide
Connect a Framer CMS project with API credentials so approved articles can be pushed into the right collection.
API key
Auth
Draft/live
Modes
Queue
Runtime
Connect a Framer CMS project with API credentials so approved articles can be pushed into the right collection.
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.
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.
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.
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
Open the audit, onboarding, or publishing workflow and keep the next action tied to a real business profile.