Skip to main content
You cannot edit a live connection in place, and pausing it does not make it editable. Instead, Synclify gives you an editable draft: a copy you change freely, validate, preview, and then promote.
Pausing is not editing. Paused connections reject edits — the API returns errors. If you paused a connection hoping to change its mapping, that isn’t the path. Create a draft.

​
The draft flow

1

Create the draft

Open the connection and make a change. Synclify asks: Create editable draft? Confirm.The live connection keeps running untouched while you work.
2

Make your changes

Adjust field mappings, per-field directions, sync direction, cadence, publishing, or deletion policy.
3

Save

Your changes are stored on the draft.
4

Save & Review

Synclify validates the draft and computes a preview of what the next sync would do.
5

Approve

Read the preview. Approving activates the draft, replacing the live configuration.
Drafts survive page reloads and browser restarts. Come back and Synclify picks up where you left off.

​
Discarding a draft

Changed your mind? Discard draft in the status dropdown throws the draft away and leaves the live connection exactly as it was.
Discard this draft? The active version keeps running unchanged. Unsaved draft edits, including its record pairings, are discarded.
The buttons are Keep draft and Discard draft. On success: “Draft discarded — The active version keeps running unchanged.”
Discarding takes the record pairings with it, not just the field changes. If the draft went through pairing and record decisions, that work is gone and a future draft starts the review from scratch.

​
Changing which table or collection syncs

Editing a mapping assumes both sides stay put. When the source table moved or the collection was rebuilt, use Change synced resources instead.
1

Pick the side

Source, destination, or both — then choose the replacement. The picker badges resources that are Already synced by another connection, and shows each one’s parent and account.
2

Read what changes

A plain-language review, not a confirm button: “Read this before creating the draft — re-pointing a side is not a silent swap.”
  • “Your existing record pairings will be cleared and re-reviewed. Every record is matched again from scratch.”
  • “Field mappings are carried over. Fields that do not exist on the new resource will need remapping before activation.”
  • “The current connection keeps syncing until you activate the new version.”
3

Create draft version

You land in the normal review-and-approve flow.
You can create a draft pointing at a resource another active connection already claims — but activating it will be refused until that connection is paused or archived. The dialog warns you before you start, so this is a choice rather than a surprise at the end.

​
What validation checks

The same guards as creation:
  • Every mapping is type-compatible across text / number / boolean / date-time families.
  • An identity field is set.
  • Required Webflow fields are mapped.
  • Existing records still pair correctly under the new mapping.
Warnings do not block approval. Anything reported as a warning — including “dry-run preview is only available” — lets you activate, with a toast. Only error, failed, or invalid statuses stop you.A warning still deserves a read. Warnings are how Synclify tells you a mapping is legal but probably not what you meant.

​
Changing the identity field

Possible, but think first. Changing which field identifies a record re-pairs everything. Records that paired under the old field may not pair under the new one. Synclify shows you the consequences in the preview — read the create and delete counts carefully. If Delete orphaned records is on, an identity change that fails to re-pair will delete the unmatched Webflow items and create replacements. Turn that setting off before changing identity, then turn it back on once you’ve confirmed the pairing.

​
Picking up a new source column

Adding a column in Airtable does not add it to a live connection. Mappings are fixed at activation. Create a draft, map the new column, review, approve.

​
Dialogs and background refresh

The connection page refreshes itself while you have it open. It stands down while any dialog is open, so a name you are halfway through typing into an archive or discard confirmation is never wiped by a background poll.

​
Approval hiccups

If the preview was incomplete, Synclify re-runs the full preview and retries the approval once. No action needed.
You clicked Sync now while a draft is pending. Finish the review-and-approve flow first; Sync now only works on active connections.
The message tells you: recheck the draft, and if it persists, resolve the records in Airtable or Webflow directly. Usually the new identity field’s values don’t actually match across the two sides.

​
A known limitation

Webhook-triggered syncs continue to fire against the live connection while you edit a draft. Pausing the connection is not a valid workaround, because paused connections can’t be edited.In practice: make your draft changes and approve them in one sitting rather than leaving a draft open for days.