What a Notion to Framer CMS sync actually does
A Notion to Framer sync keeps a Notion database and a Framer CMS collection matched to each other, so content written in Notion appears on the Framer website without anyone retyping it. You map each Notion property to a Framer CMS field once. After that, edits made in Notion flow into Framer CMS on their own.
KnotCMS does not replace Framer CMS. Framer CMS is still the CMS your website reads from, and your Framer project stays exactly as you built it. KnotCMS sits alongside it as the pipe that keeps it fed, which means nothing about your existing layouts, components, or publishing workflow has to change.
The practical effect is that the person who writes the content and the person who owns the design no longer need to be the same person — and no longer need to be in the same tool.
Connect Notion to Framer CMS in five steps
Setup happens once per site and takes about five minutes. You need edit access to the Framer project and to the Notion database; your client needs neither until the last step.
- 1. Connect the Framer project. In Framer, create a Server API key for the project and paste it into KnotCMS. This is what lets the sync write to your CMS collections from outside the editor.
- 2. Connect the Notion database. Authorise KnotCMS in Notion and pick the database that holds the content. Notion only exposes pages you have explicitly shared with the integration, so share the database first if it does not appear in the list.
- 3. Map the fields. Match each Notion property to the Framer CMS field it feeds — title to title, rich text to formatted text, files to image, and so on. Anything you leave unmapped is ignored rather than guessed at.
- 4. Choose the slug field. Every CMS item needs one unique, non-empty slug. Pick the Notion property that supplies it, and make sure no two rows share a value — duplicate and blank slugs are the single most common reason a sync stops. What to do when a sync fails covers how to find them.
- 5. Share the Notion page with your client. They need nothing else — no Framer account, no new tool to learn. From here, their edits are the trigger.
Which Notion property becomes which Framer field
Most of the mapping is obvious. The rows below are the ones where the obvious choice is not the right one, or where a decision you make once is awkward to change later.
| Notion property | Framer CMS field | What to watch for |
| Title | Title (plain text) | This is the item name shown in the CMS, not the page URL. The URL comes from whichever property you pick as the slug, which is a separate choice — if your titles are rendering as my-great-post, the slug got mapped into the title. |
| Rich text | Formatted text or plain text | Decide deliberately. Formatted text keeps bold, italics, links and line breaks, but the styling travels with the content and Framer text styles cannot restyle it. Plain text can be styled freely in Framer and drops the formatting. Changing your mind later means re-mapping. |
| Select, Status | Option | The option list is captured when the field is created. Adding or renaming an option in Notion afterwards needs a re-map, and a blank Select can display as the first option rather than as empty — see Select fields not showing correctly. |
| Multi-select | Plain text | There is no multi-value equivalent in a single field. It syncs as a comma-separated string. Real per-tag filtering needs a second collection and references. |
| Date | Date | Straightforward. Decide whether you need the time component before mapping. |
| Created time, Last edited time | Date | Created time is reliable. Last edited time is not a "last updated" stamp — Notion bumps it on any edit at all, including fixing a typo in a field you never display, so it will claim a page changed when nothing visible did. If the date is shown to visitors, use a date property you set by hand. |
| Number | Number | Notion number formatting (currency, percent) is display-only and does not travel. Format it in Framer. |
| Checkbox | Toggle | Maps cleanly. Useful for a Featured or Published flag you control from Notion. |
| URL, Email, Phone | Link | Framer buttons and link elements only accept a Link field as their destination — a URL sitting in a text field cannot drive a button. Map it to Link. Email and phone become working mailto: and tel: links. |
| Files & media | Image, Gallery or File | One property can become a single image, a gallery of every image on the row, or a downloadable file. Pick per field. |
| Formula, Rollup | Whatever the result is | Lands in the field type matching the computed result — number, toggle, date or text. |
| Relation | Not supported by KnotCMS | Framer's own Notion plugin does map relations onto CMS reference fields. KnotCMS does not yet, so flatten the value to text with a Notion formula if you need it today. |
If a column is missing in Framer rather than mapped wrongly, it is usually because it was added in Notion after setup. Re-open the connection and step through to the field mapping screen — new properties appear there, and your existing fields keep whatever you have already bound them to.
What happens after a client makes an edit
Your client edits content in Notion, in the workspace they already use every day. KnotCMS picks up the change and syncs it straight into your Framer CMS collection.
Crucially, updates land in Framer as drafts. Nothing goes live because someone typed a sentence in Notion. You review the change and publish when you are ready, which keeps a review step between your client and your production website.
If a site does not need that gate, you can turn it off. Auto-publish pushes synced changes live without the manual step, which suits content types where speed matters more than review — a changelog, a job board, a frequently updated blog.
How is this different from Framer's own Notion plugin?
Framer ships a free official Notion plugin, and for a site you maintain yourself it is a good choice. The difference is where the sync runs. The plugin syncs when a collaborator opens it inside the Framer editor and clicks sync. KnotCMS runs on its own servers: on a paid plan it checks Notion once a minute, reconciles the Framer CMS collection, and optionally publishes, with nobody opening Framer. That is the property that makes a client handoff work.
Framer's on-page editing is a different answer again: the client edits the live site directly, which needs a content editor seat in your project. The full comparison lays out when each of the three makes sense.
Why not just copy content into Framer CMS by hand?
Because it never stays copied. Framer is where you design and ship. Notion is where most clients already write. Without a sync layer in between, every headline change, new blog post, and updated team bio arrives as a message to you, and you become the transcription step between the two tools.
That cost is easy to underestimate. A single content update is only a few minutes of work, but it arrives unscheduled, it interrupts design work, and it repeats every week for every client site you have shipped. For a freelancer with five live sites, routine content edits quietly become a recurring part-time job that nobody is paying for.
Giving the client Framer access is the obvious escape hatch, and it is usually the wrong one. Framer is a design tool. Handing a non-technical client the keys to fix a typo means they are one misclick away from a broken layout, and it means paying for another Framer seat on a project that has already been delivered.
Who this is for
KnotCMS is built for the handoff problem specifically: Framer freelancers and agencies who have delivered a site and do not want to stay permanently attached to it as the content editor.
It is a good fit when your client can write in Notion but should not be in Framer, when you are maintaining several live Framer sites at once, or when adding client seats to Framer is not worth the cost or the risk on a delivered project — the general case for client content management without Framer access.
It is not the right tool if your client genuinely needs to change design or page structure. That is what Framer itself is for, and no sync layer substitutes for it.
What it costs
The free plan covers one site. It syncs once a day and allows 10 syncs in total, with up to 50 CMS items per sync, which is enough to connect a real client site and see the workflow end to end before committing.
Starter is $9 a month, or $85 a year, for one site and adds syncs every minute, unlimited syncs, and optional auto-publish. Studio covers 5 sites for $39 a month and Agency covers 20 for $99. A site that is live and being maintained costs less per month than the time it takes to hand-copy a single round of content edits.
Common questions
How long does it take to connect Notion to Framer?
About five minutes per site: connect your Framer project with a Server API key, authorise the Notion database, map your Notion properties to the matching Framer CMS fields, choose a slug field, and share the Notion page with your client. You only do this once per site.
Do my clients need a Framer account?
No. Your client only needs access to the connected Notion page. They never sign in to Framer, which means no extra Framer seats and no risk of accidental design changes.
Does KnotCMS replace Framer CMS?
No. Framer CMS remains your website's CMS. KnotCMS keeps it updated from your Notion database, so your Framer project, layouts, and publishing flow stay exactly as they are.
Will a client edit go live on my site immediately?
Not by default. Synced updates arrive in Framer CMS as drafts, so you review and publish them yourself. If you would rather skip that step, auto-publish can be enabled per site.
Why does my Notion database not show up when I connect it?
Notion only exposes pages that have been explicitly shared with the integration. Open the database in Notion, use the share menu to add the KnotCMS integration, then refresh the database list. The same rule applies to the official Framer plugin.
Why not give clients access to Framer instead?
Clients usually only need to edit content, and Framer is a design and development tool. Notion is far simpler for non-technical users, and keeping clients out of Framer avoids both extra collaborator seats and the risk of a layout being broken by someone trying to fix a typo.
Is Google Sheets supported?
Not yet — Google Sheets support is planned. KnotCMS is designed to support additional content sources over time, with Notion as the first.
