Integrations · Marketing

Connect Windsor.ai to Well

Name: Windsor.ai entities in Well
Creator: Well

Attribute Windsor.ai attribution event, channel, and campaign to revenue in your CRM, with channel and cohort breakdown ready.

Connect Windsor.aiSee what Well does

What Well pulls from Windsor.ai

Windsor.ai feeds attribution event, channel, campaign into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Windsor.ai’s access.

From Windsor.ai	In Well	Relation
Attribution event	Marketing signal	Feeds
Channel	Category	Groups under
Campaign	Outreach record	Resolves to

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Windsor.ai → Well

What Well does with your Windsor.ai connection

Connect

Connect Windsor.ai over OAuth (MCP DCR): Well registers a client through Windsor.ai's OAuth Dynamic Client Registration and you approve on Windsor.ai's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings attribution event, channel, and campaign in from Windsor.ai on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Windsor.ai entity into marketing signal, category, and outreach record, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Windsor.ai lands in the workspace as marketing signal, category, and outreach record you can search, chart, and automate.

Questions Windsor.ai unlocks

Ask in plain language. Well answers from your connected Windsor.ai connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Windsor.ai connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Windsor.ai connection…

Connect Windsor.ai in three steps

01
Authorise Windsor.ai via MCP
From Well's Connections panel, search for Windsor.ai and click Connect. Well discovers Windsor.ai's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Windsor.ai's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.windsor.ai
02
Map your entities
Well's MCP client discovers attribution event, channel, and campaign from Windsor.ai that Windsor.ai's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
03
Use the data
Ask questions in conversation, build records tables, or let agents act on Windsor.ai records. Because Windsor.ai ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Windsor.ai records happens in the background.

How Windsor.ai stays secure with Well

Well connects to Windsor.ai's MCP server (mcp.windsor.ai) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Windsor.ai secret. Tokens are scoped to the attribution event, channel, and campaign Windsor.ai exposes and refreshed server-side. Reads only, Well cannot modify or delete Windsor.ai records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.windsor.ai

Read Windsor.ai records
Resources the Windsor.ai MCP server exposes, scoped by your OAuth approval.
granted
Resolve attribution event, channel, and campaign across your stack
Match identifiers in Windsor.ai against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Windsor.ai records
Not granted; Windsor.ai is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Windsor.ai passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Windsor.ai’s admin panel.

Frequently asked questions about Windsor.ai and Well

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

Well brings in attribution event, channel, and campaign from Windsor.ai and reshapes each entity into your workspace: attribution event becomes marketing signal; channel becomes category. Every record arrives with the source identifier preserved, so Windsor.ai stays the source of truth while Well lets you query the data alongside the rest of your stack.

Well attributes each Windsor.ai campaign to the customers it acquired, joining campaign spend and engagement records to deal stages and invoiced revenue. Blended CAC, channel-level payback, and cohort behaviour are queryable without a separate attribution stack.

Every workspace marketing signal built from Windsor.ai carries the source attribution event identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Windsor.ai record; from Windsor.ai, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.

Well combines live Windsor.ai events with periodic reconciliation reads of attribution event, channel, and campaign. New rows appear within seconds when Windsor.ai pushes them; periodic reads catch anything a push missed. The first connect backfills history from Windsor.ai in the background.

Open Connections > Windsor.ai in Well and click Disconnect. Well calls Windsor.ai's token revocation endpoint and stops calling Windsor.ai immediately on its side; provider-side propagation to Windsor.ai's admin panel varies by provider. The attribution event, channel, and campaign Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Windsor.ai 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.

Ready to connect Windsor.ai?

Connect once. Every attribution event, channel, campaign from Windsor.ai becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.

Connect Windsor.aiTalk to us