Skip to main content
A connection binds one Airtable table to one Webflow CMS collection. Building one takes four steps, and then guided setup reconciles whatever already exists on both sides. Start at Connections → New connection.
Nothing is written to Webflow during the wizard. The connection is created as a draft and stays inert until you approve the first preview.

​
Step 1 — Destination

Pick the Webflow site, then the CMS collection to sync into.
Wizard step 1: choosing a Webflow CMS collection from a dropdown of available collections

Each collection shows its field count, so you can tell them apart at a glance.

Webflow collection already connected. A collection can back only one live connection. Claimed resources carry an Already synced badge in the dropdown, so you see it before you pick rather than after you submit.What the badge tells you depends on who holds the claim:
  • Someone in your workspace — the message names the connection holding it and offers a button to open it. Pause or archive that connection to free the resource.
  • Another workspace — you’re told the resource is already synced, and nothing about the other tenant is revealed.
Either way, Continue stays blocked until you pick something free.
Choose the destination first because it determines the field list you’ll map into — including which fields Webflow marks required.

​
Step 2 — Source

Pick the provider, then the specific resource.
  • Airtable — choose a base, then a table.
  • Google Sheets and Notion — visible but disabled, both marked Coming soon.
Wizard step 2: Airtable selected as the source with a table dropdown; Google Sheets shown as Coming soon

Select Airtable, then pick the table to sync from.

If your Airtable account isn’t listed, connect it first from Data Sources.

​
Step 3 — Map fields

Synclify auto-maps on entry, matching source column names to Webflow field names and known aliases. It takes a moment. Auto-mapping is deliberately conservative. It matches on name evidence only — an exact key, a full token match, a known synonym — and never on field type or position. It then assigns globally: the strongest pair is settled first and both fields are consumed, so one source column can never be auto-mapped onto two Webflow fields. A column called Name does not land on Job Title just because nothing better was found. Manual mapping has no such restraint. Anything auto-mapping declined to guess, you can still map yourself.
Wizard step 3: Airtable source columns mapped to Webflow CMS fields, with the Slug row marked as the ID field

Each Webflow field shows its type (PlainText, Switch, Reference…). Unmatched fields read '— not mapped —'; the row marked ID field is the record identifier.

Then you:
  • Review each mapped pair and correct the wrong ones.
  • Set the ID field — required.
  • Add mappings for columns auto-mapping missed, and remove ones you don’t want synced.
Incompatible pairs block Continue. Required Webflow fields cannot be removed. Where a pair can be written one way but not read back, Synclify says so here and disables Two-way with the reason, rather than accepting the mapping and failing at creation. This step has enough depth to deserve its own page: Field mapping.

​
Step 4 — Settings

Wizard step 4: connection settings with sync direction, polling cadence, auto-publish on, and delete orphaned records off

Name the connection, set direction and cadence, then Create connection. Realtime is included regardless of cadence.

​
required
How the connection appears in lists, history, and the delete confirmation. Use something you’d recognize under pressure — Blog posts → Webflow, not Connection 3.
​
one-way | two-way
default:"one-way"
One-way (Source updates Webflow) — Airtable is the source of truth; Webflow edits to mapped fields are overwritten.Two-way (Shared fields can update both sides) — edits flow both ways, and you get per-field ownership.
​
manual | polling
default:"manual"
Manual — syncs only when you click Sync now.Polling — a fallback scan every N minutes, hours, or days.Realtime sync runs regardless of this setting. Polling exists to catch what webhooks miss.
​
toggle
default:"on"
On: synced items are published live. Off: they land in Webflow as staged changes for someone to publish by hand.
​
toggle
default:"off"
Off: a Webflow item whose source row disappeared is left alone.On: it is permanently deleted from Webflow.
Minimum poll interval is 5 minutes. Anything shorter is rejected: “Minimum poll interval is 5 minutes to avoid rate-limit issues.” Tighter polling gets you rate-limited by Airtable and Webflow, which makes syncs slower, not faster. Realtime already covers the sub-minute case.
Delete propagation is destructive and permanent. A source row deleted by accident — or an identity value someone renamed — will delete the matching Webflow item on the next sync. Leave this off unless deletions in the source genuinely mean “unpublish from the site.”New connections are delete-safe by default, and turning propagation on later requires ticking an explicit acknowledgement as well as the toggle — see Sync settings.

​
When creation is blocked

Two things can stop a connection before the wizard’s final step, and both tell you before you click rather than refusing afterwards.
Your plan caps how many connections can be active at once. When you’re at the cap, a banner names the limit and Create is disabled. Pause or archive a connection, or upgrade.
When the workspace’s billing state would cause activation to be refused, an inline notice appears up front — with a pre-filled support draft — instead of letting you build a connection that cannot be activated. See Billing.
The wizard is a write action. A viewer who types the URL is redirected rather than shown a form they cannot submit — see roles.

​
If a provider’s resources won’t load

A per-account banner shows the provider’s own message rather than an empty dropdown. If Airtable has hit a monthly API limit, that is what it says — which is far more useful than “no tables found”.

​
Leaving mid-wizard

Your progress is saved to this browser as you go, so reloading the page resumes exactly where you were. Navigating away deliberately still prompts:
Leave connection setup? Your setup will be discarded and you’ll have to start over.
A saved wizard draft is cleared on sign-out and on workspace switch. If you are midway through a setup, finish it or note your choices before switching workspaces — see switching workspaces.

​
After the wizard

Synclify creates the draft and immediately starts guided setup — pairing existing records, collecting your decisions about unmatched ones, resolving conflicts, and previewing the first sync before anything is written.