integrations

Framer troubleshooting

When the feed URL or the AnySync mapping acts up.

tip

Most of the issues below are 5-minute fixes. If you'd rather hand it off, email support@quibo.cc and a real human answers within one business day.

"Missing token" or "Invalid token" from the feed

The feed only answers when the per-site token is present and matches. AnySync shows a 401 with one of those messages.

Fix: open Sites, then your site in Quibo and copy the Feed URL from the Framer feed URL panel again, including the ?token= part, then paste it into the AnySync API URL field. If your plugin sends the token as a header instead, use Authorization: Bearer <token>. The token only changes when you regenerate it from the site page (Regenerate feed token in the Credentials card): the old feed URL stops working at once and the new one must be pasted into AnySync.

Posts arrive but fields are empty

Make sure every field you need (title, slug, html, excerpt, metaTitle, metaDescription, coverImageUrl, coverImageAlt, language, author, publishedAt, aiAssisted, aiDisclosure, faq, jsonLd) is mapped to a CMS field in AnySync.

Field names in the feed are fixed and case-sensitive. If you renamed a collection field in Framer, update the mapping on the plugin side.

Articles don't show up in Framer

Only articles with status Published in Quibo are in the feed. An article in Ready or Scheduled is not served yet: click Publish now on its page, or wait for its scheduled time.
AnySync imports on its polling interval. Check the interval you set (15 minutes is the default we suggest) and trigger a manual sync in the plugin if it offers one.
The feed returns the 50 most recent published articles by default (up to 200 with ?limit=). If your plugin polls with ?since=, an older article that was published after a newer one may be skipped; run a full sync once.

Refreshed articles create duplicates

When Quibo refreshes an article, the new copy keeps the original's id in the feed and replaces it at the same slug. Key your AnySync sync on the id field (or on slug) so the existing Framer item is updated instead of a second one being added.

JSON-LD doesn't render in `<head>`

Framer doesn't auto-render <script> from CMS string fields. You need a Code Override that injects the jsonLd field into <head>. Example:

import type { ComponentType } from "react";

export function withJsonLd(Component: ComponentType): ComponentType {
  return (props) => {
    const data = (props as { jsonLd?: unknown }).jsonLd;
    return (
      <>
        {data ? (
          <script
            type="application/ld+json"
            dangerouslySetInnerHTML={{ __html: JSON.stringify(data) }}
          />
        ) : null}
        <Component {...props} />
      </>
    );
  };
}

Apply it on your blog post template.

Test connection passes but nothing syncs

Test connection only checks that the site has a well-formed feed token; it does not contact Framer. Verify the full path by publishing one article and waiting for the next poll cycle, or by opening the feed URL in a browser: you should see a JSON object with an items array.

Still stuck?

Email support@quibo.cc with the organization ID shown in Settings, Account. Business plans get priority routing, with a typical response under 8 business hours.

If you'd rather start clean: connecting the site again in Quibo gives you a fresh feed URL, and pasting it into a new AnySync configuration usually works on the first try. Connect a new site