Connect Coupler.io to Well

From Well, open Connections, find Coupler.io, and click Connect. Well discovers the OAuth metadata at mcp.coupler.io/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Coupler.io's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in imported row, spreadsheet, and schedule from Coupler.io and reshapes each entity into your workspace: imported row becomes indexed record; spreadsheet becomes workspace context. Every record arrives with the source identifier preserved, so Coupler.io stays the source of truth while Well lets you query the data alongside the rest of your stack.

Well tracks the last sync watermark per table and only requests rows that changed since then, using whatever incremental marker Coupler.io exposes (last_updated, sequence_id, or partition key). Backfills run in the background on first connect; subsequent reads stay cheap and the load on Coupler.io's side stays bounded.

Well watches for updates to imported rows and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right indexed record. Edits flow in incrementally; nothing is duplicated, and the Coupler.io source identifier is retained on every revision.

Well combines live Coupler.io events with periodic reconciliation reads of imported row, spreadsheet, and schedule. New rows appear within seconds when Coupler.io pushes them; periodic reads catch anything a push missed. The first connect backfills history from Coupler.io in the background.

Open Connections > Coupler.io in Well and click Disconnect. Well calls Coupler.io's token revocation endpoint and stops calling Coupler.io immediately on its side; provider-side propagation to Coupler.io's admin panel varies by provider. The imported row, spreadsheet, and schedule Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Coupler.io records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.