Integrations · observability

Connect Axiom to Well

Connect Axiom so its record, owner, and timestamp become queryable in conversation and through your agents.

What Well pulls from Axiom

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

From Axiom	In Well	Relation
Record	Graph node	Becomes
Owner	Team member	Resolves to
Timestamp	Audit entry	Anchors

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

What Well does with your Axiom connection

Connect

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

Sync

Well brings record, owner, and timestamp in from Axiom 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 Axiom entity into graph node, team member, and audit entry, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Axiom lands in the workspace as graph node, team member, and audit entry you can search, chart, and automate.

Questions Axiom unlocks

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

Ask Well

Ask anything about your Axiom connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Axiom connection…

1 agent skill runs on Axiom.

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

Connects and checks Axiom

Check your connections

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

Browse all skills

Connect Axiom in three steps

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

How Axiom stays secure with Well

Well connects to Axiom'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 Axiom secret. Tokens are scoped to the record, owner, and timestamp Axiom exposes and refreshed server-side. Reads only, Well cannot modify or delete Axiom records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

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

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

Frequently asked questions about Axiom and Well

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

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

What does Well pull into the workspace from Axiom?

Well brings in record, owner, and timestamp from Axiom and reshapes each entity into your workspace: record becomes graph node; owner becomes team member. Every record arrives with the source identifier preserved, so Axiom stays the source of truth while Well lets you query the data alongside the rest of your stack.

What does Axiom unlock once it is connected to Well?

Once Axiom is connected, every record it exposes is queryable from conversation, filterable in records tables, and available to your agents through your workspace. The data stays linked to its Axiom source, so you can always trace a workspace record back to the original.

How does Well match a record from Axiom to a graph node in my workspace?

Each Axiom record is scored against the candidate graph nodes in your workspace on identifier overlap, amount or quantity match, date proximity, and counterparty resolution. Matches above the auto-link confidence threshold flow through cleanly; below the threshold they queue for a one-click human review, with the most likely graph node prefilled and the Axiom source attached.

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

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

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

Open Connections > Axiom in Well and click Disconnect. Well calls Axiom's token revocation endpoint and stops calling Axiom immediately on its side; provider-side propagation to Axiom's admin panel varies by provider. The record, owner, and timestamp 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 Axiom?

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