Skip to main content
Mapping tells Synclify which Airtable column feeds which Webflow field. Get it right here and syncs are boring, which is what you want.

​
Auto-mapping

When you land on the mapping step, Synclify matches source columns to Webflow fields by name and known aliases. It takes a second or two. Auto-mapping is a starting point, not an answer. Always review it. It matches on names, so two similarly-named fields can get crossed.

​
The ID field

Exactly one mapped pair must be marked Use as ID field. Synclify uses it to decide whether an Airtable row and a Webflow item are the same record. Synclify preselects slug, name, or title when one exists.
Without it you cannot continue: “Identity strategy is required — Map at least one matching field, such as slug or name, before creating the connection.”
Pick a column that is unique per row and doesn’t get rewritten. Changing an identity value in the source makes Synclify treat the row as a new record — it loses track of the existing Webflow item. Identity-mapped fields have their direction locked.
Field Mappings tab pairing Airtable columns with Webflow CMS fields, with a Field Owner column and the slug row marked as the ID field and labelled Identity record field

Each pair shows its source column, its Field Owner, and the Webflow field. Here slug is the ID field, so its direction is locked.

​
Type compatibility

Synclify sorts field types into four families and refuses to map across them: Mapping a text column into a number field blocks Continue.
Compatibility is resolved per field pair from the backend, which also decides which ownership directions each pair supports. The families below describe the usual outcome; the answer Synclify gives for a specific pair is the authoritative one.Some pairs can be written one way but not read back. Those are flagged here, at the mapping step, and the Two-way option is disabled with the reason — rather than accepting the mapping and failing later at creation.If compatibility can’t be resolved, Synclify stops rather than guessing: “Compatibility for this field pair could not be verified. Refresh the provider schema and try again.”
Fix a mismatch by remapping to a compatible field, or by changing the column type in Airtable.

Field compatibility reference

The full table of which Airtable columns map to each Webflow field type — plus images, references, and columns that don’t map.

​
Adding and removing fields

Add a mapping for any source column that auto-mapping missed. Remove any mapping you don’t want synced — an internal Airtable column, a formula field, a notes column.
Required Webflow fields cannot be removed. Webflow rejects items missing them, so the mapping stays. If you see “Required field cannot be removed”, map something into it — or make the field optional in Webflow.

​
Per-field direction (two-way only)

On a two-way connection, each mapped field has its own direction. Click the toggle beside a field to cycle through:
Source writes, Webflow doesn’t. Webflow edits to this field are discarded on the next sync.
Webflow writes, source doesn’t. The column is read but never applied.
Either side writes. Simultaneous edits to the same record raise a conflict.
Two exceptions, both enforced:
  • slug is always Airtable owns. Webflow derives and validates slugs; two writers means broken URLs.
  • The identity field’s direction cannot be changed. A record renamed on both sides can’t be matched.
A good default for two-way: everything Airtable owns except the handful of fields designers actually touch in Webflow — hero image, SEO title, a layout flag. You keep one-way discipline on copy without locking anyone out.

​
Changing a mapping later

Mappings are fixed once the connection is live. Add a column to Airtable and it will not appear in an active connection. To change one, create an editable draft, adjust the mapping, then review and approve. Synclify re-runs validation and shows a preview before anything changes.