Each of these builders connects with an API key or token. Start in Settings → Integrations and pick your platform.
Webflow
In Webflow, open Site Settings → API Access and generate a site token that can read sites and manage CMS content.
In Citera, choose Webflow → Connect with API Key and paste the token. No OAuth redirect is needed.
Citera loads your sites and defaults to one. Change it if needed.
Note: Webflow static pages can't be edited over the CMS API, and Webflow products publish through the full editor.
Wix
Generate a Wix API key with Wix Data/CMS read and write access.
Find your Site ID in your Wix dashboard URL.
In Citera, choose Wix, and enter the API key and Site ID.
Wix Code (Velo) must be enabled on the site.
Framer
Open your Framer project in the browser and copy the URL from the address bar. Any editor, published or project link works.
In Framer, go to Site Settings → General → API Keys and generate a new key.
In Citera, choose Framer, and paste the project URL and API key.
Under Blog Publishing Target, pick the CMS collection for blog posts (or leave it on auto-detect by name) and set the blog post URL pattern using [slug], for example /blog/[slug].
Tip: in Framer, open your /blog page and check the right-side panel to see which collection it's bound to. If no collections are found, create one in Framer first. Framer keeps serving the previous build until you publish the site.
Disconnecting
You can disconnect from the integration's settings. Content already published isn't affected, and for Framer your API key is deleted from Citera's vault.