Cover Image or Published Date is empty in the CMS row

The collection is missing a field for it. Add an Image field named Cover Image (or Hero / Featured / Thumbnail) and a Date field named Published Date, then republish. Azuqe matches by field name.

The blog opens but shows the Framer template's Title / Description

The Framer page template isn't reading from the CMS item. In the Framer editor, edit the blog page's SEO settings and bind the meta title + meta description to your CMS collection's Title and Summary fields.

No writable CMS collection found

Framer projects need at least one collection with a Rich Text field for Azuqe to publish into. Create one under CMS → New Collection.

Category shows Blog instead of the real category

Add a Category field to the collection (Enum with your category names, or Plain Text). Azuqe will match by name; without the field it falls back to Blog.

Connection test fails

Regenerate the API key inside Site Settings → API and paste the fresh value. Framer keys can be revoked when the project is duplicated.

Integration Guide

Framer

Publish blog posts as items in a Framer CMS collection.

How It Works

Every post you publish becomes a new item in your Framer CMS collection. Title, content, cover image, category and publish date are filled in automatically. Republish updates the same item; the change is live as soon as Framer re-publishes the collection.

Setup Steps

Open your Framer site settings

Open your Framer project in the editor.
Click your project name in the top-left, then choose Site Settings.

Open Site Settings from the project menu

Open General settings

In the left sidebar of Site Settings, click General.
You'll see your Project ID here. Keep this tab open — you'll copy it in a moment.

Click General in the Site Settings sidebar

Copy your Project ID

Under General → Project ID, click Copy.
This is the ID Azuqe uses to find your site.

Project ID lives near the top of General

Copy your API key

Still in Site Settings, scroll down to the API section.
Click Generate API key (or copy the existing one).
Framer only shows the key once — paste it in Azuqe right after generating.

Scroll to the API section and generate or copy the key

Set up your CMS collection

Open your Framer project → CMS in the left sidebar.
Use (or create) a collection named Blog, Posts, or Articles.
Recommended fields: Title (Plain Text), Slug (Plain Text), Content (Rich Text / Formatted Text), Cover Image (Image), Category (Enum or Plain Text), Published Date (Date).
Azuqe fills each of these automatically by field name — the field types must match.

Connect in Azuqe

Open Connected Apps → Framer → Connect.
Paste your Project ID and API key; click Connect.
After a publish, open your CMS and confirm the row shows Title, Content, Cover Image, and Published Date filled in.

After connecting, publish a blog and check the row in Framer's CMS to verify the Cover Image and Published Date show up

What Gets Synced

Blog posts become native CMS items — no manual copy-paste.

Cover image, category, and published date are filled in automatically.

Republish updates the same CMS item — no duplicates.

Rich text content preserves headings, lists, images, and links.

Troubleshooting

Ready to connect?

Open your dashboard and navigate to Connected Apps to link Framer.

All Platforms Go to Dashboard