Integrations · API

Connect B2B Wave to Well

Push person record into Well through B2B Wave, ready to query and act on in your workspace.

What Well pulls from B2B Wave

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

From B2B Wave		In Well	Relation
Person record		Contact	Resolves to

Sync mode: incremental polling
Refresh: scheduled
Direction: B2B Wave → Well

What Well does with your B2B Wave connection

Connect

Connect B2B Wave over API key: you generate a B2B Wave key and paste it into Well, where it is stored encrypted at rest and never returned in responses.

Sync

Well brings person record in from B2B Wave on a recurring poll that fetches only what changed since the last read. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each B2B Wave entity into contact, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

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

Questions B2B Wave unlocks

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

Ask Well

Ask anything about your B2B Wave connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your B2B Wave connection…

1 agent skill runs on B2B Wave.

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

Connects and checks B2B Wave

Check your connections

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

Browse all skills

Connect B2B Wave in three steps

01
Generate an B2B Wave API key
In B2B Wave, generate an API key with the scopes Well lists in the trust section below. In Well's Connections > B2B Wave, paste the key. Well validates it against B2B Wave's API and confirms with a sample fetch.
- AuthAPI key
- Validationsample fetch on save
02
Map your entities
Well brings person record from B2B Wave into your workspace using the canonical mappings defined in Well's data-views layer.
- Mappingpreconfigured by Well
03
Use the data
Use what you bring in from B2B Wave in conversation, records tables, or agent runs. Rotating the key in B2B Wave requires updating the key in Well; nothing else.
- First syncstarts as soon as connect completes

Keys are never returned in API responses. Rotate freely; Well will prompt for the new key.

How B2B Wave stays secure with Well

Well calls B2B Wave with the API key you provision, scoped to person record. The key is never logged and never returned in API responses. B2B Wave validates the key on every request; rotating the key in B2B Wave immediately invalidates Well's access. No write access unless the key explicitly grants it.

API keyEncrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

Read B2B Wave records
Endpoints the B2B Wave API token grants, scoped by your consent.
granted
Resolve person record across your stack
Match identifiers in B2B Wave against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete B2B Wave records
Not granted; B2B Wave is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Read API keys from B2B Wave's settings
Well only sees the keys you paste in. The keys never leave Well's secret store back to B2B Wave's admin surface.
refused

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

Frequently asked questions about B2B Wave and Well

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

In B2B Wave, generate an API key with read access (scoped to what's listed in the security section below). In Well, open Connections > B2B Wave, paste the key, and save. Well validates the key against B2B Wave's API and pulls a first sample as confirmation.

What does Well pull into the workspace from B2B Wave?

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

What does B2B Wave unlock once it is connected to Well?

Once B2B Wave 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 B2B Wave source, so you can always trace a workspace record back to the original.

How does Well match a person record from B2B Wave to a contact in my workspace?

Each B2B Wave 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 B2B Wave source attached.

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

Well polls B2B Wave regularly for person record. The first connect pulls the historical window your account allows; subsequent reads only fetch what changed since the last sync, so the load on B2B Wave's side stays modest.

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

Open Connections > B2B Wave in Well, click Disconnect, then rotate the API key on B2B Wave's side. Well stops calling B2B Wave as soon as you disconnect; rotating the key on the provider's side guarantees Well cannot resume access. The person record already synced stay in your workspace until you ask Support to purge them.

How does Well protect what it pulls in from B2B Wave?

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