Connect Windsor

Before you connect

You need a Windsor account with at least one source account connected. In Windsor, open the source you want, sign in to that service, choose the relevant account or accounts, and finish the authorization flow. Windsor lists connected accounts in its Data Sources area.

Follow Windsor's official connector setup guides for source-specific permissions and steps. Loam only reads from the sources you have already connected in Windsor; it does not connect to or change those services for you.

Find your Windsor API key

Sign in to Windsor, open Settings, then open the API Access section and copy your API key. Treat the key like a password. Paste it only into Loam's connection dialog; do not add it to a Table, query, or support message.

Connect Windsor in Loam

Windsor appears as a choice only when it is enabled for your workspace. You need Admin access at the workspace root to create or change the connection.

1. Open Settings > Integrations (sign in to open this page).
2. Choose Connect provider, then choose Windsor.
3. Give the connection a name that identifies this Windsor login, paste your Windsor API key, and start the connection.
4. Review the sources and Tables Loam says it will sync. Loam begins the initial import only for supported profiles.

Loam keeps Windsor to one connection per workspace because its Tables are provider-wide. Native account-scoped providers may allow several named connections; for those providers, enter the exact advertising account IDs that each credential is allowed to import. Loam validates the full list and does not automatically add other accounts visible to that credential.

What Loam imports

A source being available in Windsor does not automatically make every field or Table a supported Loam integration. Loam imports only the versioned source profiles shown as supported in the connection detail. A source shown as unsupported is not imported. Connect a supported source in Windsor, then return to Loam and retry discovery.

Imported Tables use a stable path such as integrations.windsor.facebook_ads.campaigns. The source account is recorded with the rows instead of becoming another dataset in the path. Everyone with Viewer or stronger access can query the Tables normally, but the complete integrations hierarchy is system managed. Users and agents cannot edit its rows, schema, datasets, or grants.

Follow the first import and later refreshes

Open the Windsor connection to see each supported stream separately. Its detail shows the destination, current state, last successful refresh, imported row count, and any safe recovery message. A queued or backfilling stream is still working. A degraded connection can contain both current Tables and another stream that needs attention.

Scheduled refreshes revisit a recent window so Windsor corrections and late activity can update existing rows without creating duplicates. An Admin can choose Sync now when a fresh run is needed.

Recover a sync

Incomplete

Loam could not prove that it received every row for one part of the import, so it did not mark that part complete. Follow the stream message and retry after the issue is resolved. Previously completed data and checkpoints remain available.

Authentication paused

The Windsor key is invalid, expired, revoked, or no longer permitted. An Admin should copy the current key from Windsor and choose Replace key in Loam. Existing Tables remain readable while the connection is paused.

Waiting for Windsor quota

Loam waits until Windsor's displayed reset time instead of repeatedly requesting data. No action is normally needed. If the delay continues beyond that time, retry the stream once.

If the status still does not move, follow the connection errors checklist and include the redacted status message when you use Loam's Support button. Never include your Windsor key.

What happens when you disconnect

Disconnecting deletes the stored credential and stops future sync work. It does not delete imported data. The existing integrations.windsor datasets and tables remain readable through normal workspace permissions and remain system managed. You cannot edit or delete them through ordinary Loam, API, SQL, or agent actions after disconnecting.