Skip to main content
Airtable today. Google Sheets and Notion are on the roadmap — they appear in the app marked Coming soon or aren’t selectable yet. Webflow is always the destination.
Usually seconds. Realtime sync is included on every plan — Synclify watches your source and runs a sync as soon as it detects a change. Optional polling is a fallback for anything webhooks miss.
Yes, on a two-way connection. You control it field by field with per-field ownership — copy owned by Airtable, visuals owned by Webflow, for example. Simultaneous edits to the same field raise a conflict you resolve.
Not without your say-so. Guided setup pairs existing records, asks what to do with unmatched ones, surfaces conflicts, and shows a full preview before the first write. Webflow items with no source row can be kept untouched.
Only if you turned on Delete orphaned records (off by default). With it off, the Webflow item stays. See Sync settings.
Mappings are fixed once a connection is active. Create an editable draft, change the mapping, review, and approve. Pausing the connection does not make it editable.
Polling has a 5-minute minimum, but you rarely need it — realtime already delivers changes in seconds. Tighter polling just burns API quota. See Sync settings.
A column that’s unique per row and never rewritten — a slug, a name, or a dedicated ID. It’s how Synclify matches rows to Webflow items. Changing an identity value makes Synclify see a brand-new record. See Identity field.
Yes. Connect additional Webflow accounts and sites from Data Sources. Each Webflow CMS collection can back one live connection at a time — a claimed collection shows an Already synced badge in the wizard, and you free it by pausing or archiving the connection holding it.
OAuth — you authorize on the provider’s site and Synclify never sees your password. Webflow access is scoped to CMS read/write only. Details on the Security page.
Workspace health lists everything needing attention across every connection and connected account, worst first. The Health entry in the sidebar carries a badge with the count.
Usually not. Synclify names the reason — most often “Source-only rows were left out of Webflow, as configured.” or “Webflow-only items were left unmanaged, as configured.”, which are your own guided setup decisions being honoured. See Sync history.
A conflict is a value fight: both sides changed the same two-way field, and you choose which wins. A difference is a pairing or structural problem — records that don’t line up — and deciding it records a decision without changing any data. See Differences.
Within its retention window, yes — but restoring re-links the copy that still exists rather than recreating what the provider deleted. See Deleted records.
Use a kill switch in Security settings. Pause all syncing blocks new runs and cancels in-flight ones; Pause reverse syncing is the surgical option when bad edits are flowing back into your source.
Only if you let them, only for as long as you allow, and never silently. Access is a time-boxed grant you issue with a reason, it expires on its own, and everything they open is recorded. See Support access.
Five roles — Owner, Admin, Operator, Viewer, Support. See Team.
When Synclify hits an error it offers a pre-filled support report — accept it. Or email help@synclify.cloud. See Troubleshooting first for the common ones.