Integrations · PayrollConnect Deel (Token) to Well
Connect Deel (Token) so its person record, company record, invoice, and transaction become queryable in conversation and through your agents.
What Well pulls from Deel (Token)
Deel (Token) feeds person record, company record, invoice into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Deel (Token)’s access.
| From Deel (Token) | In Well | Relation | |
|---|---|---|---|
| Person record | Contact | Resolves to | |
| Company record | Customer | Enriches | |
| Invoice | Receivable | Becomes | |
| Transaction | Ledger line | Becomes |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Deel (Token) → Well
What Well does with your Deel (Token) connection
Connect
Connect Deel (Token) over OAuth (MCP DCR): Well registers a client through Deel (Token)'s OAuth Dynamic Client Registration and you approve on Deel (Token)'s side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings person record, company record, and invoice in from Deel (Token) 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 Deel (Token) entity into contact, customer, and receivable, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Deel (Token) lands in the workspace as contact, customer, and receivable you can search, chart, and automate.
Questions Deel (Token) unlocks
Ask in plain language. Well answers from your connected Deel (Token) connection, resolved against the rest of your stack.
Ask anything about your Deel (Token) connection
Ask about your Deel (Token) connection…
1 agent skill runs on Deel (Token).
Well lists Deel (Token) in the connection check every skill runs before it answers. No skill reads it for a figure yet.
Connects and checks Deel (Token)
Connect Deel (Token) in three steps
- 01
Authorise Deel (Token) via MCP
From Well's Connections panel, search for Deel (Token) and click Connect. Well discovers Deel (Token)'s MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Deel (Token)'s side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- 02
Map your entities
Well's MCP client discovers person record, company record, invoice, and transaction from Deel (Token) that Deel (Token)'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 Deel (Token) records. Because Deel (Token) 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 Deel (Token) records happens in the background.
How Deel (Token) stays secure with Well
Well connects to Deel (Token)'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 Deel (Token) secret. Tokens are scoped to the person record, company record, invoice, and transaction Deel (Token) exposes and refreshed server-side. Reads only, Well cannot modify or delete Deel (Token) records.
- granted
Read Deel (Token) records
Resources the Deel (Token) MCP server exposes, scoped by your OAuth approval.
- granted
Resolve person record, company record, invoice, and transaction across your stack
Match identifiers in Deel (Token) against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Deel (Token) records
Not granted; Deel (Token) is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Deel (Token) passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Deel (Token) and Well
How do I connect Deel (Token) to Well, and how long does it take?
From Well, open Connections, find Deel (Token), and click Connect. Well discovers the OAuth metadata from Deel (Token)'s MCP server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Deel (Token)'s side. No client_id or client_secret to paste; the handshake takes roughly a minute.
What does Well pull into the workspace from Deel (Token)?
Well brings in person record, company record, invoice, and transaction from Deel (Token) and reshapes each entity into your workspace: person record becomes contact; company record becomes customer. Every record arrives with the source identifier preserved, so Deel (Token) stays the source of truth while Well lets you query the data alongside the rest of your stack.
What does Deel (Token) unlock once it is connected to Well?
Once Deel (Token) 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 Deel (Token) source, so you can always trace a workspace record back to the original.
How does Well match a person record from Deel (Token) to a contact in my workspace?
Each Deel (Token) person record is scored against the candidate contacts 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 contact prefilled and the Deel (Token) source attached.
How often does Deel (Token) sync with Well, and what triggers a refresh?
Well combines live Deel (Token) events with periodic reconciliation reads of person record, company record, invoice, and transaction. New rows appear within seconds when Deel (Token) pushes them; periodic reads catch anything a push missed. The first connect backfills history from Deel (Token) in the background.
Can I disconnect Deel (Token) and what happens to the data Well already pulled?
Open Connections > Deel (Token) in Well and click Disconnect. Well calls Deel (Token)'s token revocation endpoint and stops calling Deel (Token) immediately on its side; provider-side propagation to Deel (Token)'s admin panel varies by provider. The person record, company record, invoice, and transaction 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 Deel (Token)?
The Deel (Token) records Well holds are encrypted at rest and handled in line with GDPR. See /privacy for the current data-handling policy.
Pairs well with Deel (Token)
More in Payroll
Popular cross-category
Ready to connect Deel (Token)?
Connect once. Every person record, company record, invoice from Deel (Token) becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.