Skip to main content
Retiring a connection is a single action: Delete. It stops all sync jobs and moves the connection to your Archive, where it’s kept for history along with the reason you gave.
Deleting is a soft action. The connection leaves your active list but is retained in the Archive as a record — it isn’t wiped. The in-app confirmation is worded strongly (“permanently delete… cannot be undone”) because it stops syncing and there is no self-serve restore, but the connection and its reason remain visible in the Archive.

​
What deleting does

  • Stops all sync jobs immediately. The connection no longer reacts to source changes, schedules, or manual runs.
  • Moves the connection to Archive, tagged with the reason you entered.
  • Leaves your Webflow CMS items in place. The items this connection created stay in your site — nothing will update them again.
  • Leaves your Airtable data untouched.

​
What deleting does not do

  • It does not delete the CMS items in Webflow.
  • It does not touch your source data.
  • There is no in-app restore today. The Archive is a read-only history. To sync the same source and collection again, create a new connection.

​
Delete a connection

1

Open the connection

Go to the connection’s detail page.
2

Find the Danger Zone

Scroll to Danger Zone and click Delete.
3

Read the confirmation

“This will permanently delete <connection name> and stop all sync jobs.” In practice the connection is retained in your Archive — but syncing does stop.
4

Type the exact name

Character for character. This guards against retiring the wrong connection.
5

Give a reason

Free text, required. It’s stored with the connection and shown in the Archive.
6

Confirm

The connection stops syncing and moves to Archive.
Both the name and the reason are required — the confirm button stays disabled until both are filled.

​
The Archive

Retired connections live under Archive in the sidebar. It’s a read-only list showing each connection and the reason it was retired — useful for auditing what once synced into a collection and why it was stopped. The Archive doesn’t sync anything and doesn’t block other actions.

​
When you have to delete

Two situations in the app require retiring a connection first:
A Webflow collection can back only one live connection. To point a different source at a collection that’s already connected, delete the existing connection first.“Webflow collection already connected — Delete the existing connection for this Webflow collection before creating another one.”
An account can’t be disconnected while a live connection depends on it. Delete the dependent connections first — once archived, they no longer block. The dialog lists up to five blockers.“Delete active connections before disconnecting this data source.”

​
Before you delete

1

Check what depends on it

Deleting leaves the CMS items in place but stops updating them. If this connection is the only thing keeping a collection current, its content will go stale.
2

Note the configuration

Mapping, direction, and per-field ownership go with the connection, and there’s no restore. Rebuilding a large mapping by hand is tedious — capture it if you might need it again.