Visual changes to the sync connector picker

Visual changes to the sync connector picker. Easier to read and search to find your connector.

‍

Also this week

• New screen for initial sync. Partially rolled out last week, now it's used everywhere. More clear instructions and workflow.
• Google Sheets permission errors simplification. Better instructions, and inline action buttons.
• Google Sheets setup stops before it writes anything if a selected tab has a merged cell in the header row. It names the tabs and links Google's docs, instead of failing partway through on creating the Whalesync ID column.
• A Webflow site publish that Webflow refuses now shows Webflow's own reason — "a full site publish is required," for example — and points you at the Webflow Designer.
• In the table mapper, setting the last two-way column to one-way turns the table one-way to match, so you can't end up creating empty records on the other side. Clicking an arrow the table doesn't allow offers to make the table two-way instead. The field list header stays put while you scroll.
• Listing a side's bases over the public API or MCP when its authorization is broken now comes back as a connection error that says it needs reconnecting, rather than a generic server error you could retry forever.
• Supabase started rejecting our token refresh on September 12. Affected syncs keep running on their stored credentials, the connection is flagged for reconnection with an email, and it clears itself once Supabase accepts us again.
• Attio locations: a city, state or country part not synced to Attio could fail the push outright, or go out empty and clear what Attio had.
• Postgres databases behind AWS RDS Proxy couldn't be connected at all. Session timeouts are applied after connecting now rather than in the startup packet, which poolers reject.
• Two MCP tools were failing on their own: record status when the table wasn't given as a table id, and field listings run in parallel against Postgres and Webflow sides.
• Reauthorizing a sync with unchanged credentials returned a server error. Nothing was lost — the reauthorization finished either way — but the error is gone.
• A WordPress connection created through the public API without a site URL reported success and then failed later when fetching previews. It's rejected up front.
• Turning a sync on while its initial sync is still applying is refused, instead of killing the initial sync partway through and marking it failed.