Integrations · Data

Connect Enigma to Well

Materialise Enigma company record and document into your workspace, queryable in conversation and through agents.

What Well pulls from Enigma

Enigma feeds company record, document into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Enigma’s access.

From Enigma		In Well	Relation
Company record		Customer	Enriches
Document		Source document	Captures as

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Enigma → Well

What Well does with your Enigma connection

Connect

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

Sync

Well brings company record and document in from Enigma through live reads, backed by a periodic reconciliation pass. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Enigma entity into customer and source document, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Enigma lands in the workspace as customer and source document you can search, chart, and automate.

Questions Enigma unlocks

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

Ask Well

Ask anything about your Enigma connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Enigma connection…

1 agent skill runs on Enigma.

Well lists Enigma in the connection check every skill runs before it answers. No skill reads it for a figure yet.

Connects and checks Enigma

Check your connections

See what is connected, what is syncing, and what is missing.

Browse all skills

Connect Enigma in three steps

01
Authorise Enigma via MCP
From Well's Connections panel, search for Enigma and click Connect. Well discovers Enigma's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Enigma's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
02
Map your entities
Well's MCP client discovers company record and document from Enigma that Enigma'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 Enigma records. Because Enigma 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 Enigma records happens in the background.

How Enigma stays secure with Well

Well connects to Enigma's MCP server via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Enigma secret. Tokens are scoped to the company record and document Enigma exposes and refreshed server-side. Reads only, Well cannot modify or delete Enigma records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

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

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

Frequently asked questions about Enigma and Well

How do I connect Enigma to Well, and how long does it take?

From Well, open Connections, find Enigma, and click Connect. Well discovers the OAuth metadata from Enigma's MCP server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Enigma's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

What does Well pull into the workspace from Enigma?

Well brings in company record, and document from Enigma and reshapes each entity into your workspace: company record becomes customer; document becomes source document. Every record arrives with the source identifier preserved, so Enigma stays the source of truth while Well lets you query the data alongside the rest of your stack.

How does Well materialise Enigma data into your workspace?

Well materialises selected tables or queries from Enigma into your workspace. New rows flow in incrementally on a cadence you set; downstream agents and dashboards see the same canonical entities as the rest of your workspace, with the Enigma source link preserved.

What happens when Enigma updates a company record that Well already pulled in?

Well watches for updates to company records 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 customer. Edits flow in incrementally; nothing is duplicated, and the Enigma source identifier is retained on every revision.

How often does Enigma sync with Well, and what triggers a refresh?

Well combines live Enigma events with periodic reconciliation reads of company record and document. New rows appear within seconds when Enigma pushes them; periodic reads catch anything a push missed. The first connect backfills history from Enigma in the background.

Can I disconnect Enigma and what happens to the data Well already pulled?

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

How does Well protect what it pulls in from Enigma?

The Enigma records Well holds are encrypted at rest and handled in line with GDPR. See /privacy for the current data-handling policy.