Integrations · Productivity

Connect Nylas to Well

Index Nylas person record so questions about contact answer themselves in conversation.

What Well pulls from Nylas

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

From Nylas		In Well	Relation
Person record		Contact	Resolves to

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

What Well does with your Nylas connection

Connect

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

Sync

Well brings person record in from Nylas 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 Nylas entity into contact, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Nylas lands in the workspace as contact you can search, chart, and automate.

Questions Nylas unlocks

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

Ask Well

Ask anything about your Nylas connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Nylas connection…

1 agent skill runs on Nylas.

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

Connects and checks Nylas

Check your connections

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

Browse all skills

Connect Nylas in three steps

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

How Nylas stays secure with Well

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

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

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

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

Frequently asked questions about Nylas and Well

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

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

What does Well pull into the workspace from Nylas?

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

How does Well surface Nylas mentions of my customers and deals?

Every Nylas 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 Nylas tasks and threads that mention them, ranked by recency and reach.

How does Well preserve the link from a workspace contact back to the original person record in Nylas?

Every workspace contact built from Nylas carries the source person record identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Nylas record; from Nylas, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.

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

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

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

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

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