SyncFlow

A Webflow collection is a good place to publish content, but it is rarely where the content gets written. Drafting and editorial review usually happen somewhere else, so someone ends up pasting finished copy into a collection item field by field, then pasting it again every time an editor rewrites a sentence.

SyncFlow closes that gap for one specific writing surface. It reads a Notion database, maps each property to a field in a Webflow CMS collection, and writes the content across in one direction, either on demand or automatically whenever a Notion page changes. Because it is a Webflow Marketplace app, the connection is authorized through OAuth instead of custom code.

It fits teams that publish on a regular cadence from a shared editorial database: blogs, product changelogs, documentation, help articles. If your writers work in Notion databases and your site runs on Webflow, SyncFlow takes the copy step out of the middle. If the source content lives anywhere other than Notion, this is not the app for that job.

How to integrate SyncFlow with Webflow

What is SyncFlow? SyncFlow is a Notion to Webflow content sync app built by the independent developer behind the @ybouane account and listed on the Webflow Marketplace, where it carries our app review badge. It converts Notion blocks into Webflow rich text, keeps code formatting and mathematical notation intact, and can publish the updated items to your live site.

Most setups need nothing beyond the app itself. The SyncFlow app install handles authorization for both accounts and the field mapping between a Notion database and a Webflow collection. The sync configuration decides whether content moves on its own or only when you trigger it. The Webflow Data API route is the fallback for anything SyncFlow does not do, such as writing back to Notion or syncing from a source other than Notion.

Install the SyncFlow app

This is the only supported no-code path, and the one the vendor documents. Install order matters more than the vendor guide suggests: build the Webflow collection before you connect anything, because the mapping screen can only offer fields that already exist.

To set up the sync:

1. Create the destination collection in Webflow first, with a field for every Notion property you plan to bring across, including the rich text field that will hold the page body.
2. Install SyncFlow from its Webflow Marketplace listing and authorize it against the site that holds that collection. The app asks to read and write CMS data and to access site data.
3. Sign in on the SyncFlow site and connect your Notion account, granting access only to the databases you want synced rather than the whole workspace.
4. Map each Notion property to its Webflow field. Supported types include text, images, checkboxes, dates, and URLs.
5. Run one manual sync against a single Notion page and check the result in the collection before you switch auto-sync on.

Because SyncFlow reads and writes CMS data, the site needs a plan that includes the CMS. The Marketplace listing still shows the older CMS plan label, which Webflow merged with Business into the Premium site plan. The vendor's paid tier covers a single site install, so a second Webflow site means a second subscription.

Map fields and choose a sync mode

Once the mapping exists, the rest of the setup is deciding how much of the pipeline runs without you. SyncFlow documents these behaviors:

• Auto-sync: Any Notion page created or edited inside a connected database reaches the mapped Webflow collection with no manual trigger.
• Auto-publish: Synced changes go live on the site instead of sitting as staged edits, which suits a blog and does not suit a page waiting on legal review.
• Page linking: Links between Notion pages are rewritten as links between the matching Webflow items, so internal cross references survive the move.
• Code highlighting: Notion code blocks arrive formatted and highlighted, which is the difference between usable and unusable developer documentation.
• TeX rendering: Mathematical expressions written in Notion render on the Webflow side, which matters for academic and technical publishing.
• Styling control: Imported Notion elements can carry inline styles or classes. Classes are the better choice, because they let your existing Webflow styles govern the output.

Content that lands in the collection behaves like any other CMS content from that point on, so a Collection List renders it with no special handling. One tradeoff to plan around: the sync runs one way, so an edit made directly on a synced item in Webflow can be overwritten the next time that Notion page changes.

Build a custom sync with the Webflow Data API

SyncFlow publishes no public API reference and no webhook documentation, so it cannot be driven from outside the app. When you need two-way sync, a source other than Notion, or sync logic tied to your own systems, write against the Webflow Data API v2 and host that service yourself.

Start by authenticating with a site token or an OAuth bearer token in the Authorization header. From there you create collection items with POST /v2/collections/{collection_id}/items and update existing ones with PATCH against the same path plus the item id, then publish those items with POST /v2/collections/{collection_id}/items/publish. You can also register webhooks on events such as collection_item_changed so your service reacts when someone edits an item in Webflow.

This is real backend work, and the tradeoff deserves saying plainly: the app costs a few dollars a month and takes an afternoon, while a custom sync is a service you then own and maintain.

What you can build with the SyncFlow Webflow integration

Every pattern below assumes Notion holds the source text while Webflow holds the design and the published page.

The combination fits these workflows:

• Editorial blog pipeline: Writers draft and review inside a Notion database with its own status property, and approved posts sync into the blog collection on their own.
• Developer documentation: Engineers write docs next to their work in Notion, and code blocks reach the site formatted rather than flattened into plain paragraphs.
• Product changelog: A release database in Notion becomes the public changelog, so shipping a note is a row in a table instead of a separate CMS chore.
• Technical or academic library: Course notes and reference pages that rely on mathematical notation publish with their expressions intact.

If you would rather own the pipeline than rent it, get started with the CMS API and build the same flow from your own source of truth.

Content operations get easier when the site itself is queryable by an agent. Connect the Webflow MCP server to your workspace and you can audit a collection and check what a sync actually wrote without leaving the session where you review the draft.