Connect Framer

Modern Framer (2026+) doesn't accept incoming webhook posts to its CMS. Instead, you install a CMS sync plugin in your Framer project and point it at an external feed. Quibo provides that feed: a per-site URL that returns your published articles as JSON, on demand.

In Quibo (1 minute)

1. From Sites, then Connect a site pick Framer.
2. Enter your site name, your Framer site URL (used for brand voice extraction) and the output language. You don't need to paste any credentials.
3. Click Connect site.

Quibo generates a unique feed URL for this site automatically.

In Framer (3 minutes)

1. Open your Framer project, then Plugins, and install AnySync (free).
2. Open the CMS collection that should receive blog posts (or create one).
3. Click the AnySync plugin in the sidebar and find the API URL field.
4. Back in Quibo, open Sites, then your site and copy the Feed URL from the Framer feed URL panel at the top. Paste it into AnySync.
5. Map the JSON fields to your collection fields (one-time):
   • title to your Title field (Plain Text)
   • slug to your Slug field (Plain Text)
   • html to your Body / Rich Text field
   • excerpt to your Summary / Excerpt field (Plain Text)
   • coverImageUrl to your Cover Image field (Image, Framer fetches the URL)
   • coverImageAlt to your Cover image alt field (Plain Text)
   • author to your Author field (Plain Text)
   • metaTitle and metaDescription to your SEO Title / Description fields (optional)
   • publishedAt to your Published Date field
   • aiDisclosure to an AI disclosure field (Plain Text, optional)
6. Set the polling interval (15 minutes is a sensible default).
7. Save.

When an article goes live in Quibo (you click Publish now, or its scheduled time arrives), it appears in the feed immediately and AnySync inserts it into your CMS at the next poll cycle.

What we serve

Each article comes back as a flat JSON object in items[]:

{
  "id": "uuid",
  "title": "...",
  "slug": "...",
  "html": "<h2>...</h2><p>...</p>",
  "excerpt": "The meta description.",
  "metaTitle": "...",
  "metaDescription": "...",
  "ogTitle": "...",
  "ogDescription": "...",
  "coverImageUrl": "https://...",
  "coverImageAlt": "...",
  "jsonLd": { "@context": "https://schema.org", ... },
  "language": "en",
  "author": "Editorial Team",
  "faq": [{ "question": "...", "answer": "..." }],
  "publishedAt": "2026-05-10T...",
  "aiAssisted": true,
  "aiDisclosure": "..."
}

Only articles with status Published are listed, newest first. The feed accepts ?limit= (default 50, max 200) and ?since=<iso> for incremental polling, if your plugin supports it. The token is accepted either as ?token= in the URL or as an Authorization: Bearer <token> header.

When the site's AI disclosure is on (the default), the disclosure sentence is appended as the last paragraph of html and also exposed on its own as aiDisclosure, so you can map it to a dedicated field instead.

When Quibo refreshes an article, the new copy keeps the original's id in the feed, so a sync plugin keyed on id updates the existing Framer item instead of adding a second one.

Author selection

The author field carries the Default author saved in the brand profile of Sites, then your site. Framer has no API to list users, so today the only byline on offer is Editorial Team, which is also what the feed uses when nothing is saved.

Test the connection

In Sites, then your site click Test connection: we verify the feed token is present and well formed (no call to Framer is made). To smoke-test the full path without waiting for an article to be generated, our team can trigger a test article via an internal endpoint; ask in support if needed.

Security

• The feed URL contains a per-site token. Treat it like a password: anyone with the URL can read your published articles.
• Rotate the token from the site page in Quibo: Regenerate feed token in the Credentials card issues a new one and the old URL stops working at once. Paste the new feed URL into AnySync.
• Past articles published before the token rotation remain in your Framer CMS. Only future fetches are affected.

Retention

For every other CMS, Quibo removes the article body 30 days after publishing because the CMS holds the live copy. Framer is different: AnySync reads the feed Quibo serves, so published articles stay complete in Quibo for as long as the site is connected and keep being served by the feed. Deleting the site removes them from the feed; what AnySync then does with the items already in your Framer CMS depends on the plugin, so export or duplicate anything you want to keep before deleting a Framer site.