Integrations · Productivity

Connect Amie to Well

Index Amie task, assignee, and project so questions about work item and team member answer themselves in conversation.

What Well pulls from Amie

Amie feeds task, assignee, project into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Amie’s access.

From Amie	In Well	Relation
Task	Work item	Indexes as
Assignee	Team member	Resolves to
Project	Workspace context	Groups under

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

What Well does with your Amie connection

Connect

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

Sync

Well brings task, assignee, and project in from Amie 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 Amie entity into work item, team member, and workspace context, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Amie lands in the workspace as work item, team member, and workspace context you can search, chart, and automate.

Questions Amie unlocks

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

Ask Well

Ask anything about your Amie connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Amie connection…

1 agent skill runs on Amie.

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

Connects and checks Amie

Check your connections

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

Browse all skills

Connect Amie in three steps

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

How Amie stays secure with Well

Well connects to Amie'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 Amie secret. Tokens are scoped to the task, assignee, and project Amie exposes and refreshed server-side. Reads only, Well cannot modify or delete Amie records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

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

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

Frequently asked questions about Amie and Well

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

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

What does Well pull into the workspace from Amie?

Well brings in task, assignee, and project from Amie and reshapes each entity into your workspace: task becomes work item; assignee becomes team member. Every record arrives with the source identifier preserved, so Amie stays the source of truth while Well lets you query the data alongside the rest of your stack.

Can Well show me which Amie owners are active on which workspace entities?

Each Amie item carries its assignee, which Well resolves into a workspace team member entity. Asking "who on the team owns Globex in Amie right now" returns the assigned people across active Amie items, joined to their workspace identity, so you see ownership across tools in one query.

How does Well match a task from Amie to a work item in my workspace?

Each Amie task is scored against the candidate work items 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 work item prefilled and the Amie source attached.

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

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

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

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

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