Integrations · Data

Connect Bright Data to Well

Materialise Bright Data company record, person record, and document into your workspace, queryable in conversation and through agents.

Connect Bright DataSee what Well does

What Well pulls from Bright Data

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

From Bright Data	In Well	Relation
Company record	Customer	Enriches
Person record	Contact	Resolves to
Document	Source document	Captures as

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

What Well does with your Bright Data connection

Connect

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

Sync

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

Available

Your data from Bright Data lands in the workspace as customer, contact, and source document you can search, chart, and automate.

Questions Bright Data unlocks

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

Ask Well

Ask anything about your Bright Data connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Bright Data connection…

1 agent skill runs on Bright Data.

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

Connects and checks Bright Data

Check your connections

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

Browse all skills

Connect Bright Data in three steps

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

How Bright Data stays secure with Well

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

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

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

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

Frequently asked questions about Bright Data and Well

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

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

What does Well pull into the workspace from Bright Data?

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

How does Well materialise Bright Data data into your workspace?

Well materialises selected tables or queries from Bright Data into your workspace. New rows flow in incrementally on a cadence you set; downstream agents and dashboards see the same canonical entities as the rest of your workspace, with the Bright Data source link preserved.

How does Well match a company record from Bright Data to a customer in my workspace?

Each Bright Data company record is scored against the candidate customers 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 customer prefilled and the Bright Data source attached.

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

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

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

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

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

Ready to connect Bright Data?

Connect once. Every company record, person record, document from Bright Data becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.

Connect Bright DataTalk to us