Webflow CMS syncing requires some infrastructure due to the API rate-limits. You can’t just update 1,000 records, you have to manage that over a 10 minute window.
Some considerations;
Whalesync offer 2-way sync, PIP offers external-to-Webflow, so consider where your source of truth is.
Check that the external db is supported. PIP supports Airtable. Whalesync has a range of connectors including Airtable, Supabase, and a lot of SaaS platforms.
Airtable seems to be the favourite external database for Webflow CMS.
PowerImporter is great if you have one source of truth such as Airtable that you need to sync to Webflow.
Whalesync provides two-way sync between various data sources, including Airtable, and Webflow. Their plans are more expensive than PowerImporter, so it will depend on your budget.
To answer your question on reference fields, these will not managed by Zapier.
That is where PowerImporter and Whalesync can really help, as they both handle these smoothly.
Another powerful tool is Byteline data sync. It integrates with Airtable and PostgreSQL (if you choose Xano) and handles single- and multi-reference Webflow collection fields.
Other features:
Easily configure a 2-Way or 1-Way sync, turn it live, and data will keep on syncing.
Historical sync will automatically update your pre-existing data.
Not sure if you’re still looking for a solution here, but did just want to mention that we (Whalesync) just opened up some new pricing tiers so can actually be less expensive than some of the other options listed here depending on your use case.
But, in general, echoing the statements above that Airtable seems to be far and away the backend of choice for Webflow CMS. We see Notion a decent amount and occasionally Postgres, but Airtable gives a great mix of power and ease-of-use that I’d highly recommend.