Integrations · Design

Connect Figma to Well

Name: Figma entities in Well
Creator: Well

Track Figma file, project, editor, and comment alongside the deals and engineering work each one influences.

What Well pulls from Figma

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

From Figma	In Well	Relation
File	Indexed asset	Becomes
Project	Workspace context	Groups under
Editor	Team member	Resolves to
Comment	Audit entry	Captures as

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

What Well does with your Figma connection

Connect

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

Sync

Well brings file, project, and editor in from Figma 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 Figma entity into indexed asset, 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 Figma lands in the workspace as indexed asset, workspace context, and team member you can search, chart, and automate.

Questions Figma unlocks

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

Ask Well

Ask anything about your Figma connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Figma connection…

Connect Figma in three steps

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

How Figma stays secure with Well

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

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.figma.com/mcp

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

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

Frequently asked questions about Figma and Well

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

Well brings in file, project, editor, and comment from Figma and reshapes each entity into your workspace: file becomes indexed asset; project becomes workspace context. Every record arrives with the source identifier preserved, so Figma stays the source of truth while Well lets you query the data alongside the rest of your stack.

Well tracks file and project activity in Figma as workspace entities. When you ask "what is the design team shipping for Globex" the answer joins Figma project activity to the deal stage in your CRM and any open engineering issues for that account.

Each Figma file is scored against the candidate indexed assets 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 indexed asset prefilled and the Figma source attached.

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

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

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