Integrations · Productivity

Connect Asana to Well

Name: Asana entities in Well
Creator: Well

Index Asana task, project, assignee, and milestone so questions about work item and workspace context answer themselves in conversation.

Connect AsanaSee what Well does

What Well pulls from Asana

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

From Asana	In Well	Relation
Task	Work item	Indexes as
Project	Workspace context	Groups under
Assignee	Team member	Resolves to
Milestone	Deadline	Anchors

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

What Well does with your Asana connection

Connect

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

Sync

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

Available

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

Questions Asana unlocks

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

Ask Well

Ask anything about your Asana connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Asana connection…

Connect Asana in three steps

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

How Asana stays secure with Well

Well connects to Asana's MCP server (mcp.asana.com/v2/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Asana secret. Tokens are scoped to the task, project, assignee, and milestone Asana exposes and refreshed server-side. Reads only, Well cannot modify or delete Asana records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.asana.com/v2/mcp

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

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

Frequently asked questions about Asana and Well

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

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

Every Asana record is scanned for references to companies, contacts, and deal names in your workspace. Matches are surfaced inline on each entity's workspace page: a customer's profile shows the Asana tasks and threads that mention them, ranked by recency and reach.

Yes. Asana milestones are indexed in your workspace as deadline, so questions like "show me last week's milestones from Asana" return them with the original Asana link, the workspace context, and any related records (counterparty, period, attached document) joined inline.

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

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

Asana 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.