Skip to main content

Publishing to Webflow

Connect your Webflow site with a Site API token, map fields, push posts live, schedule via Nolorem, import existing items, and troubleshoot setup.

Updated Jun 19, 2026

Nolorem publishes blog posts directly to your Webflow CMS using the Webflow Data API. No plugin is required. You connect with a Site API token, map your Nolorem fields to your collection fields once, and then push posts straight to a live Webflow CMS item.

Connect your Webflow site

  1. Go to Settings then Publishing.
  2. Select Webflow as your CMS platform.
  3. Enter your Site API token. In Webflow, find it under Site settings then Apps and integrations then API access. Generate a token with CMS read and write scope.
  4. Click Test connection to verify.
  5. Pick your Site and then your Collection from the dropdowns. There is no manual ID to look up, the lists are loaded from Webflow.

Map your fields

After you pick a collection, Nolorem shows one row per Nolorem field (title, slug, body, excerpt, featured image, meta title, meta description, focus keyword, categories, tags). Each row has a dropdown of your collection's live Webflow fields, with a sensible match suggested automatically.

  • For any row you can switch to a fixed value instead of a field, and type a static value.
  • If your collection has a required field that has no matching Nolorem source, Nolorem warns you and blocks Save until you map it or give it a fixed value.
  • Your mapping is saved per blog, so different blogs can target different collections.

The field list is read live from Webflow every time you open the mapping, so renaming or adding a field in Webflow is picked up automatically.

Push a post

  1. Open a blog post in the editor.
  2. Click Push to CMS in the post actions.
  3. Nolorem formats the body as Webflow RichText, sends your mapped fields, and creates a live CMS item.

When you publish, the item goes live on your published Webflow site immediately. Title, body, excerpt, featured image, SEO fields, categories, and tags are all filled in according to your mapping. Webflow re-hosts your featured image on its own CDN.

Update an existing post

If you edit a post that was already pushed and click Push to CMS again, Nolorem updates the same Webflow item in place. No duplicate is created, and your live site reflects the change.

Schedule a post

Webflow has no built in scheduler for CMS items, so Nolorem handles scheduling for you. When you set a post to Scheduled with a future date, Nolorem stages the item in Webflow as a draft, so it is not visible on your live site yet. At the scheduled time, Nolorem publishes it live automatically. You do not need to do anything at the publish moment.

Unpublish

Unpublishing a post in Nolorem removes the item from your live Webflow site, so its page returns a not found. The item is kept in your collection as a draft, so you can republish it later. It is never deleted.

Import existing Webflow posts

If you already have content in your Webflow collection, open Settings then Publishing and click Import existing Webflow posts. Nolorem shows a preview first: how many items it found and how many are new (not yet in Nolorem). Confirm to import. Live Webflow items come in as published, draft items as draft. Running the import again is safe, already imported items are skipped, so no duplicates are created.

Webflow setup notes

A few things are configured on the Webflow side, not in Nolorem:

  • Your Webflow site must be published at least once from the Webflow Designer. Until then, live pushes fail with a message that the site is not published.
  • Individual post pages only appear once your collection has a Collection Page template and the site has been published from the Designer. The API can create the content, but only the Designer can create the template page that renders it.
  • To show the article body on the page, add a Rich Text element to your Collection Page template and connect it to the field you mapped the body to.

Publishing is failing

If a push fails, the editor reverts the post to draft. Common causes:

  • Site not published: publish your Webflow site once from the Designer, then push again.
  • Required field not filled: if a required Webflow field is mapped to a Nolorem field that is empty, Webflow rejects the item. Add content to that field in Nolorem, or set a fixed value in the mapping.
  • New required field in Webflow: if you made a field required in Webflow after saving your mapping, reopen the mapping in Settings then Publishing and map or default it.
  • Invalid token: if you removed or rotated the Site API token in Webflow, generate a new one with CMS read and write scope and update it in Settings then Publishing.

Was this article helpful?