Skip to main content
When you map fields, Synclify checks that each source column is compatible with the Webflow field you’re pointing it at. This page is the reference for what maps to what.

​
How the type check works

Synclify sorts every field into one of four type families and requires both sides of a mapping to share a family: A mapping within the same family is allowed. A mapping across families is blocked in the wizard — you can’t continue until you fix it.
Blocking is why you’ll see Continue disabled: “This field expects a number, but the source column is a different type.” Map a compatible column, or change the column’s type in Airtable.
Compatibility is decided per field pair by the backend, including which ownership directions the pair allows. The families and tables on this page describe the typical outcome and are the right thing to plan against — but for any specific pair, the answer the app gives you at the mapping step is authoritative. Pairs that can be written but not read back are flagged there, with Two-way disabled and the reason shown. See Field mapping.

​
Webflow field reference

Every Webflow CMS field type Synclify supports, and the Airtable columns that feed it cleanly.
* Image and Multi-reference belong to the text family, so the wizard won’t block a plain-text column mapped to them. But the family check can’t see whether the value is a real image URL or a valid reference — that’s on you. Test with a few records before syncing a whole table.

​
Images and references

These fields pass the type check as text, but the source value has to be right or the record is skipped or fails at sync time.
The source column must contain a publicly reachable image URL. Webflow fetches the image and hosts its own copy.
  • An Airtable Attachment field exposes a URL you can map.
  • Keep files reasonably sized — very large images can fail to upload.
  • A private or expiring URL won’t fetch.
The source column must contain the identifiers of the items being referenced in the target Webflow collection — not their display names.
  • Sync the referenced (child) collection first, so the items exist to point at.
  • Store the referenced items’ identifiers (slug or ID) in the source column, one connection per relationship.

​
Airtable columns with no clean match

Some Airtable field types have no Webflow equivalent. Flatten them in the source before mapping:

​
Tips for clean mappings

1

Pick a stable identity field

Your ID field should be unique and unchanging — a slug or an ID, not a value people rewrite.
2

Match single-select options exactly

When feeding a Webflow Option-style field, the source values must match the allowed options exactly — watch for trailing spaces and capitalization.
3

Use ISO dates and consistent time zones

Dates sync most reliably in ISO 8601 form (2026-07-09T10:22:00Z) with both sides on the same time zone.
4

Map each field once

A source column feeds one Webflow field per connection. To fill two Webflow fields from one value, duplicate the column in Airtable.