blogr.ai

Docs

Webflow

Publish articles into a Webflow CMS collection, and the inner pages from your topical map into a second collection you choose. Each one is created as a live item through Webflow's Data API and appears on your site right away.

How it works

Webflow is a visual site builder with a built-in CMS. With the connection in place, clicking Publish creates the article as a live item in your chosen CMS collection through Webflow's Data API. The item goes straight to your live site, so there is no separate site republish to run.

Connect Webflow

  1. In Webflow, open your site's settings and go to Apps & integrations → API access.
  2. Click Generate API token and give it a name, like "blogr".
  3. Set these permissions. Every other API can stay on No access:
    • CMS: Read and write, so we can create articles in your collection.
    • Sites: Read-only, so we can list your sites and collections when you connect.
  4. Copy the token right away. Webflow shows it only once (see the Webflow docs).
  5. In your blogr.ai dashboard, open Setup → Publishing, choose Webflow, and paste the token.
  6. Save. We verify the token with Webflow. If it sees one CMS collection, that collection is selected automatically; otherwise pick which one articles should publish into.
  7. Optionally pick a second collection for the inner pages your topical map designs (pricing, comparisons, services, locations). Webflow's API cannot create static pages, so pages publish as items of that collection and appear at /{collection slug}/{page slug} — a map path like /compare/acme-alternatives/ becomes the slug compare-acme-alternatives. It must be a different collection from the articles one, with a Rich text field. Reopen the Webflow setup anytime to add it.

The chosen collection needs a Rich text field. That is where the article body lands. A website publishes to one destination, so connecting Webflow replaces any other integration on the website.

What gets published

Each article is mapped onto your collection's own fields:

  • The title and slug fill the collection's built-in Name and Slug fields.
  • The article body lands in the collection's first Rich text field as HTML: headings, paragraphs, lists, links, and images.
  • The generated share image fills the first Image field, with its alt text.
  • The meta description fills a plain text field named post-summary, summary, excerpt, meta-description, seo-description, or description when your collection has one. The SEO page title fills a field named seo-title, meta-title, or page-title.
  • The publish date fills a date field named published-date, publish-date, published-on, post-date, or date when one exists.
  • Inner pages follow the same field mapping into the pages collection. Without a pages collection they wait in the workspace for you to place on the site.

Fields your collection does not have are skipped, and extra fields in the collection stay untouched. The article's URL on your site is recorded on the article in your workspace.

Failed deliveries and retries

If Webflow rejects a publish, say an expired token, a deleted collection, a required field we could not fill, or a rate limit, the article is marked "Failed to publish" in your workspace with the reason on the row. Fix the cause (or reconnect in Setup → Publishing) and click Retry publish.

Good to know

  • Publishing an article again updates the existing item in the collection instead of creating a duplicate.
  • Your token is stored encrypted and is never shown again after saving. Paste a new one anytime to rotate it.
  • You can switch the target collection anytime by reopening the Webflow setup and picking another.
  • Webflow site tokens expire after 365 days without use. Publishing through the connection keeps yours active.
  • Webflow's plan limits on CMS items apply, and Rich text keeps only the HTML elements Webflow supports.