Skip to main content
The wizard creates a draft. Guided setup is what happens next — the part that keeps Synclify from trampling data you already have. Most collections aren’t empty when you connect them. There are Airtable rows with no Webflow item, Webflow items with no row, and records on both sides whose values disagree. Guided setup resolves all three before the first sync writes anything.

​
1. Auto pairing

Synclify matches existing source rows to existing Webflow items on the identity field, using exact matches only. The matched records are shown in a table for you to check.
“Auto-pair is not available for this draft — Save the required existing-data decision instead.”Not an error. Some drafts can’t be auto-paired; skip to the decisions below and Synclify proceeds normally.

​
2. Record decisions

Whatever didn’t pair needs a decision. You get up to two, and each is required if its count is above zero.
“N source rows ready to sync, but Webflow has no matching CMS items.”Choose Create Webflow items. Synclify creates a CMS item for each on the first sync.
“N Webflow CMS items not present in source.”Choose Keep untouched. They stay in Webflow, and this connection will never update or remove them.This is the safe default and usually the right one — those items are typically older content that predates your source table.

​
3. Conflicts

For records paired on both sides whose values disagree, Synclify asks who wins: the source, or Webflow. It won’t guess. Pick per conflict, then continue. Details on how conflicts work in general: Conflicts.

​
4. Preview and approve the first sync

Synclify computes the complete first sync — every page of it — and shows you what it will do: which items get created, which get updated, which get deleted, which get skipped. Read it. This is the last checkpoint before Webflow changes. Approve activates the connection.
Warnings do not block activation. Validation results that are warnings — including “dry-run preview is only available” — let you proceed, with a toast. Only genuine errors (error, failed, invalid) block. If a warning looks material, cancel and investigate rather than clicking through.

​
5. First sync

The manual sync fires automatically the moment the connection activates. Direction is bidirectional for two-way connections, source-to-destination otherwise. You’ll see: “Your connection is active now. The first sync has started automatically.” After a 10-second countdown you’re redirected to the connection page, where you can watch the live phases.

​
If setup stalls

The full message tells you what to do: recheck the draft after the mapping update. If validation still reports unpaired records, resolve them in the Airtable table or in Webflow directly, then return.Usually means the identity field can’t match anything — check that the column you chose actually holds the same values on both sides.
Contact support. Some conflicts need backend intervention.
Expected on larger tables. Synclify retries automatically. Give it a moment.
If the preview was incomplete, Synclify re-runs it in full and retries the approval. No action needed.
Progress is saved. Reopen the connection and Synclify resumes at the stage you left.

​
After activation

The connection is active. It syncs on source changes (realtime), on your polling schedule if you set one, and whenever you click Sync now. To change anything about it from here — mapping, direction, cadence — you need an editable draft.