CMS Integrations

Sitefire can push articles directly to your CMS as drafts. Currently supported: Framer and Webflow.

Framer

1. Get your Project URL

Open your project in Framer
Copy the URL from your browser’s address bar — it looks like:
```
https://framer.com/projects/YourSite--aAbBcCdD1234567890xy
```
Paste this URL into the Project URL field in Sitefire

2. Create an API key

In your Framer project, click the Framer menu (top-left) → Settings
Scroll to API and click Generate API Key
Copy the key and paste it into the API Key field in Sitefire

For step-by-step instructions with screenshots, see the Framer API key guide.

3. Select a collection

After connecting, Sitefire will show the CMS collections in your Framer project. Select the collection where you want articles to be published (e.g. “Blog Posts”).

4. Map your fields

Map each article field (Title, Body, Slug, Excerpt, Date) to the corresponding CMS field. Fields that aren’t mapped will be skipped during push.

Webflow

1. Create an API token

In the Webflow Designer , open your site and go to Site settings (Webflow menu → Site settings) → Apps & Integrations → API access
Click Generate API token
Give the token a name (e.g. sitefire) and set these permissions:

Permission	Level	Purpose
Assets	Read and write	Upload hero/OG images
Authorized User	Read-only	Token verification
CMS	Read and write	Push blog posts as drafts, upsert by slug
Components	Read-only	Verify layout compatibility
Pages	Read and write	Set meta titles, descriptions, OG tags
Sites	Read-only	List sites in workspace, read site info

All other permissions can stay at No access.

Copy the token and paste it into the API Key field in Sitefire

For step-by-step instructions with screenshots, see the Webflow API token guide.

2. Select a site

If your workspace has multiple sites, Sitefire will ask you to pick one. If you only have one site, it’s selected automatically.

3. Select a collection

Choose the CMS collection where articles will be published. Sitefire shows all collections from your selected site.

4. Map your fields

Map each article field to the corresponding Webflow CMS field. Sitefire auto-detects common field names (like “Post Body” → Body, “Name” → Title), but you can adjust the mapping.

Supported field types:

PlainText — used for Title, Slug, Excerpt
RichText — used for Body (markdown is converted to HTML automatically)
Date — used for publish date

Pushing articles

Once connected, each completed article shows a Push to [CMS] button. Articles are always pushed as drafts — you can review and publish them in your CMS editor.

If an article with the same slug already exists in your CMS, Sitefire updates it instead of creating a duplicate.

Tables in Webflow

Webflow’s rich text fields don’t support HTML tables. When your article contains tables, Sitefire converts them to a copyable HTML snippet inside a blockquote. To display the table on your site:

Push the article to Webflow
Open it in the Webflow Designer
Find the blockquote containing the table HTML
Replace it with a Custom Code embed block
Paste the HTML into the embed block