Publishing Platforms · How to

How to publish blog posts to Framer automatically

Part of the guide How to auto publish blog posts on any CMS (2026 guide)

To publish blog posts to Framer automatically, you need code: Framer's Server API, a JavaScript SDK in free open beta since 12 February 2026, can write CMS items and publish the site from a server. A common setup is a small Node service that receives each post by webhook, writes it to your blog collection and publishes. Without code, your options are manual entry, CSV import or syncing from Notion.

Your options at a glance

Framer has no simple REST endpoint for blog posts, so the choice comes down to how much code you will run. Here is how the four routes compare (as of November 2026):

Route Code needed Automatic Best for
Manual entry in the Framer CMS None No A few posts a month
CSV import None No, you import each batch Migrating an existing blog
Notion database plus Framer's Notion plugin None Partly: you write in Notion and sync Teams already writing in Notion
Webhook to a Node service using the Server API Yes, a small service Yes Scheduled or tool-generated posts

The general case for automatic publishing, and when it is a bad idea, is in the auto publishing guide.

What Framer's CMS and Server API can do

Framer's CMS stores blog posts as items in a collection, with fields such as text, formatted text, images, dates and references. Framer distinguishes "Unmanaged Collections", which are "primarily created and updated by people", from "Managed Collections", which "are primarily controlled by Plugins".

The Server API is what makes outside publishing possible. Framer describes it as a way to "update and publish your Framer projects with a simple script from any server at any time, without opening the Framer project". Key facts from Framer's documentation, checked 16 November 2026:

  • It is in open beta and "free during open beta". Framer's FAQ says pricing is "TBD" and it "will likely charge for this API on a per-use basis, with a monthly free allowance".
  • It is a JavaScript SDK over WebSockets, not REST: "we only offer a JavaScript SDK". You install it with npm i framer-api.
  • It is "not in any way transactional", so a failure halfway through a batch can leave some items written and others not.
  • API keys are bound to one project and authenticate as the user who created them. You create one under Site Settings, General.
  • Publishing is two steps: publish() creates a new preview deployment, and deploy() promotes it to production.
  • Cold starts: Framer notes the first commands "will take a second or two".

Option 1: Webhook plus a small Node service

This is the fully automatic route. Your writing tool sends each finished post as a signed JSON webhook; your service verifies it, writes the item with the Server API, and publishes.

  1. Create the collection. In Framer, add a CMS collection with fields for Title, Slug, Content (formatted text), Excerpt, Image, and a plain text field to store the sender's post ID.
  2. Create a Server API key for the project under Site Settings, General. Keep it in an environment variable such as FRAMER_API_KEY.
  3. Deploy a Node endpoint on any host that can run a long enough request. It must accept POST requests over HTTPS.
  4. Verify the webhook signature before doing anything else (example below).
  5. Upsert the item. Connect with connect(projectUrl, process.env.FRAMER_API_KEY), find the blog collection, and add or update the item using the stored post ID so updates hit the same item. The formatted text field accepts HTML by default and can take Markdown.
  6. Publish and deploy. Call publish(), then deploy() with the returned deployment ID so the post reaches the live site.
  7. Reply with the post ID and URL so the sender can link to the live post and send later updates to the same item.

One gap to test early: Framer's documentation shows item writes in detail for plugin-managed collections, and says the Server API "shares most methods" with the Plugin API, but we did not find a page that explicitly shows writing to a collection created by hand. Postbing's own Framer recipe uses a hand-made collection; confirm it works on your project before you rely on it.

Verifying a Postbing webhook in Node

Postbing signs each request with HMAC SHA-256 over <timestamp>.<raw body>, sends it as X-Postbing-Signature: v1=<hex>, and asks you to reject timestamps more than 5 minutes from your clock. For 24 hours after you rotate the secret, the header carries two comma-separated values; accept either.

import crypto from "node:crypto";

function verify(rawBody, headers, secret) {
  const ts = headers["x-postbing-timestamp"];
  const age = Math.abs(Date.now()/1000-Number(ts));
  if (age > 300) return false;
  const expected = crypto.createHmac("sha256", secret)
    .update(`${ts}.${rawBody}`).digest("hex");
  return headers["x-postbing-signature"].split(",")
    .map(v => v.trim().replace(/^v1=/, ""))
    .some(sig => sig.length === expected.length &&
      crypto.timingSafeEqual(Buffer.from(sig), Buffer.from(expected)));
}

Read the raw body before any JSON parsing, or the signature will not match. Answer with a 2xx status within 30 seconds; Postbing retries after 5 minutes, 30 minutes and 2 hours on timeouts, network errors, 408, 409, 425, 429 and 5xx. Because the Idempotency-Key header is the same on every retry, store it and skip duplicates. More on payloads and retries is in webhook publishing.

Option 2: Write in Notion, sync to Framer

If you do not want to run a server, Framer's Notion plugin lets you "connect your Notion databases to Framer CMS". Your posts live in a Notion database and the plugin brings them into a Framer collection.

Postbing can publish articles natively into a Notion database, so one no-code chain is: Postbing writes to Notion, and the Notion plugin syncs into Framer. We have not verified whether that sync runs without someone opening Framer, so expect to trigger it and publish the site yourself. Check field mapping for images and formatting on a test post first.

Option 3: CSV import for batches

For a one-off migration, Framer's CSV import maps spreadsheet columns to CMS fields. Framer's lesson advises "one header per CMS field, stable values for the slug or identifier", and reviewing the field mapping "before Framer creates or updates items". Stable slugs matter: they let a second import update posts instead of duplicating them.

Plan limits to check before automating

Your Framer plan caps the number of CMS items. As of November 2026, the Framer pricing page lists:

Framer plan Price (billed yearly) CMS items CMS collections
Basic $10 a month 1,000 2
Pro $30 a month 2,500, then $20 per 10,000 (40,000 max) 10, then $40 per 10 (40 max)
Enterprise Custom Custom Custom

Framer's Free plan FAQ lists 10 CMS collections but does not state an item limit, and custom domains need a paid plan. Drafts for CMS content, which keep items off the live site until you are ready, are available in Pro and Enterprise workspaces.

What Postbing does and does not do with Framer

Postbing has no native Framer connector. It supports Framer through its signed webhook, and its webhook documentation includes a Framer recipe that follows Option 1: a collection with Title, Slug, Content, Excerpt and Image fields, a Server API key, and "a small Node service with Framer's framer-api package that verifies the signature, upserts the item by postbing_id ... and publishes the site". Postbing says each recipe "needs a developer for about an hour" and warns that "Framer's Server API is in open beta; check Framer's changelog before relying on it in production."

If that is more engineering than you want, two alternatives avoid it: publish to a Postbing-hosted blog on a subdomain or reverse-proxied /blog path (the trade-offs are in hosted blog vs subfolder vs subdomain), or use the Notion route above. Plan details are on the pricing page, and the full webhook reference is in the webhook docs.

FAQ

Does Framer have an API for publishing blog posts?

Yes, the Server API, a JavaScript SDK that can write CMS items and publish the site from a server. As of November 2026 it is in free open beta, uses WebSockets rather than REST, and Framer says it will likely charge per use later.

Can I publish to Framer without writing code?

Yes, but not fully automatically. You can add posts by hand, import a CSV, or write posts in a Notion database and bring them in with Framer's Notion plugin.

Does Postbing integrate with Framer?

Not natively. Postbing publishes to Framer through its signed webhook and a small Node service you run, following the Framer recipe in its webhook docs, which a developer can set up in about an hour.

How many blog posts can a Framer site hold?

It depends on the plan. As of November 2026 Framer lists 1,000 CMS items on Basic and 2,500 on Pro, with paid add-ons up to 40,000 on Pro.

Do I need to publish the Framer site after adding a CMS item?

Yes for the live site. With the Server API you call publish to create a preview deployment and then deploy to promote it to production.

Sources

  • Framer developer docs, Server API introduction, quick start, reference and FAQ: capabilities, open beta, JavaScript SDK over WebSockets, not transactional, project-bound keys, publish and deploy, future pricing, accessed 16 November 2026
  • Framer updates, Server API announcement (12 February 2026): open beta and free during beta, accessed 16 November 2026
  • Framer developer docs, CMS (Plugin API): managed and unmanaged collections, field types, formatted text accepts HTML or Markdown, addItems, accessed 16 November 2026
  • Framer pricing page: CMS items and collections by plan, prices billed yearly, Free plan FAQ, checked 16 November 2026
  • Framer updates, drafts: drafts in Pro and Enterprise workspaces, accessed 16 November 2026
  • Framer Academy, CSV import lesson: header and slug advice, accessed 16 November 2026
  • Framer marketplace, Notion plugin page: connects Notion databases to Framer CMS, accessed 16 November 2026
  • Postbing webhook documentation: signature scheme, retries, idempotency key, Framer recipe, accessed 16 November 2026
  • Postbing product documentation, checked 16 November 2026: no native Framer connector, native Notion connector, hosted blog options

Last updated: November 16, 2026. Spotted an error? Email support@postbing.com and we will fix it. Editorial policy.

Try Postbing free

Postbing reads your site, plans a month of topics from what your customers search for, writes in your voice and publishes to WordPress, Shopify, Webflow or Ghost. Your first article is free.

Try Postbing free

No card needed. No link exchanges, ever.