Insights · Nov 12, 2026 · 4 min read · FAQ

Syncing Airtable, Google Sheets or your database to Webflow CMS

How a one-way sync keeps Webflow CMS items in step with Airtable, Google Sheets or your own database: stable IDs, publishing, rate limits and removals.

WEBFLOW CMS SYNCFrom a sheet or database SELLWRIGHT

Your branches, team members or listings live in Airtable, a Google Sheet or your own app's database, and the website shows them from Webflow CMS. Someone copies changes across by hand, so the site drifts: a closed location stays live, a new hire is missing, a fixed typo comes back. A one-way sync solves this by making the source the only place people edit, with Webflow as a copy that updates itself.

What does a reliable sync do on each run?

It compares the whole source with the whole collection, then makes only the changes needed. A sync that only reacts to new rows misses edits and removals, so we build every run as a reconciliation:

  1. Read every row in the source that should appear on the site.
  2. List the collection's items. List Items returns up to 100 items per page, with a pagination object (total, limit, offset) you use to fetch the rest.
  3. Match each row to an item by a stable ID.
  4. Create items that are missing, update items whose content changed, and take down items whose row has gone.
  5. Publish the changes and log what happened, with counts.

How do you match a row to the right CMS item?

Match on an ID that never changes, never on the name or slug. Names get corrected, and Webflow warns that changing an item's slug breaks links that point to the old one. Two patterns work well:

  • Store the Webflow item ID in the source. Creating an item returns its id; write it back to the row, and every later update targets that ID directly.
  • Keep the source ID in a plain text field in the collection. An Airtable record ID (it starts with rec) or your database's primary key works well, and List Items can filter on a custom field to find the matching item.

In Google Sheets, add an ID column that nobody edits, rather than relying on the row number.

Staged or live: when do changes appear on the site?

Changes appear when items are published, not when the API writes them. Create Items makes drafts (isDraft: true) by default, and setting isDraft: false only queues an item for the next site publish. There are three ways to go live:

  • Publish Items publishes the items you name and sets isDraft to false. This is our default for a sync.
  • The live endpoints, such as /items/live, create or update items and publish them in the same call.
  • Publish Site publishes everything staged across the site, not only your sync's changes, and allows one successful publish per minute.

One detail catches teams out: setting isDraft: true on a live item does not take it down. It stays published, with the new changes held in draft. An update only needs the fields that changed. This is the shape of a request to Update Items:

PATCH /v2/collections/{collection_id}/items
{
 "items": [
  {
   "id": "580e64008c9a982ac9b8b754",
   "isDraft": false,
   "isArchived": false,
   "fieldData": {
    "name": "Riverside branch",
    "phone": "+1 555 0100"
   }
  }
 ]
}

How do you stay within Webflow's rate limits?

Batch your writes, send only what changed, and wait when Webflow tells you to. Create, update and unpublish requests each accept up to 100 items, so a few hundred changes need only a handful of calls.

Over the limit, the API returns HTTP 429 Too Many Requests with a Retry-After header saying how long to wait. Our scripts pause for that long, then retry the same batch; Webflow's official SDK has exponential backoff built in. To spot changes, store a hash of each row's synced fields and skip rows that still match.

What should happen to items that leave the source?

Decide this before launch, because Webflow offers three different outcomes:

  • Unpublish: the Unpublish Live Items endpoint removes items from the live site straight away and sets them back to draft. They stay in the CMS.
  • Archive: setting isArchived: true keeps the item in the CMS and removes it from the live site at the next full-site publish. Archived items can be unarchived.
  • Delete: Webflow's help centre notes that deleted items remain live until the next full-site publish.

For listings and locations we usually unpublish, then archive, and delete only after a review period. Add a safety check too: if the source returns no rows, or far fewer than last time, stop the run and alert someone. An empty read from a broken connection should never take your whole team page down.

Make, Zapier or a small script?

Use Make or Zapier for row-by-row updates, and a small script when you need full reconciliation. Make's Webflow app includes List Items, Create, Update, Publish and Delete an Item, plus Make an API Call for anything else. Zapier's Webflow integration lists Create Item, Update Item, their live versions and Find Item.

Removals are the hard part for row-by-row automations: noticing something that is no longer there needs the full comparison above. A scheduled script does that in one pass, with batching and retries in one place. Whichever you choose, failures need an owner; our guide to Make scenario error handling covers alerts and retries.

Where to start

Write down each collection you want synced, the source it comes from, the ID you will match on and what should happen when a row is removed. That one page settles most of the build. If you would like the sync built, tested against real data and documented, our automation and integrations team can do it with you.

FAQ

Frequently asked questions

Can Webflow sync with a Google Sheet on its own?

Webflow can import a CSV file into a Collection, which copies the data in once. To keep a sheet and a Collection in step after that, something has to call the CMS API on a schedule or when the sheet changes, such as a Make scenario, a Zap or a small script.

Will the sync overwrite changes made in the Webflow Editor?

Only in the fields it sends. An update changes the fields included in fieldData and leaves the rest alone, so fields that live only in Webflow, such as an extra SEO description, stay as editors left them. Fields the sync owns are overwritten on the next run, so edit those in the source.

Can the sync link team members to their locations?

Yes, through reference fields. A Reference field takes the Webflow item ID of the linked item, and a Multi-Reference field takes a list of item IDs. Sync the locations first, keep a map of source IDs to Webflow item IDs, then sync team members with the right location IDs filled in.

Do images sync from Airtable or a spreadsheet?

Yes, as long as each image sits at a publicly reachable URL. For an Image field you send an object with a url, and Webflow uploads the file; its documentation sets a 4MB maximum per image. Send the image field only when the picture has changed, so each run doesn't upload it again.

Does a sync work on a site with several languages?

It can, but locales need explicit handling. Update Items changes only the primary locale unless the request includes a cmsLocaleId, and Create Items takes cmsLocaleIds to create linked variants in other locales. Decide before the build whether translations live in your source or are edited in Webflow.

How often should the sync run?

As often as the content needs to be fresh. Hourly or daily suits most listings, team pages and locations. If a change has to appear within minutes, trigger the sync when the source changes instead. Either way, send only rows that changed, which keeps each run quick and well inside the rate limits.

Next step

Ready for a website that sells?

Book a short call. We will look at your current site, agree what matters most and send a written scope with a fixed quote.

Book a callOr write to hello@sellwrightstudio.com