Integrations · APIConnect Cargo to Well
Push company record and person record into Well through Cargo, ready to query and act on in your workspace.
What Well pulls from Cargo
Cargo feeds company record, person record into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Cargo’s access.
| From Cargo | In Well | Relation | |
|---|---|---|---|
| Company record | Customer | Enriches | |
| Person record | Contact | Resolves to |
- Sync mode
- incremental polling
- Refresh
- scheduled
- Direction
- Cargo → Well
What Well does with your Cargo connection
Connect
Connect Cargo over API key: you generate a Cargo key and paste it into Well, where it is stored encrypted at rest and never returned in responses.
Sync
Well brings company record and person record in from Cargo 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 Cargo entity into customer and contact, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Cargo lands in the workspace as customer and contact you can search, chart, and automate.
Questions Cargo unlocks
Ask in plain language. Well answers from your connected Cargo connection, resolved against the rest of your stack.
Ask anything about your Cargo connection
Ask about your Cargo connection…
1 agent skill runs on Cargo.
Well lists Cargo in the connection check every skill runs before it answers. No skill reads it for a figure yet.
Connects and checks Cargo
Connect Cargo in three steps
- 01
Generate an Cargo API key
In Cargo, generate an API key with the scopes Well lists in the trust section below. In Well's Connections > Cargo, paste the key. Well validates it against Cargo's API and confirms with a sample fetch.
- AuthAPI key
- Validationsample fetch on save
- 02
Map your entities
Well brings company record and person record from Cargo 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 Cargo in conversation, records tables, or agent runs. Rotating the key in Cargo 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 Cargo stays secure with Well
Well calls Cargo with the API key you provision, scoped to company record and person record. The key is never logged and never returned in API responses. Cargo validates the key on every request; rotating the key in Cargo immediately invalidates Well's access. No write access unless the key explicitly grants it.
- granted
Read Cargo records
Endpoints the Cargo API token grants, scoped by your consent.
- granted
Resolve company record and person record across your stack
Match identifiers in Cargo against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Cargo records
Not granted; Cargo is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Read API keys from Cargo's settings
Well only sees the keys you paste in. The keys never leave Well's secret store back to Cargo's admin surface.
Frequently asked questions about Cargo and Well
How do I connect Cargo to Well, and how long does it take?
In Cargo, generate an API key with read access (scoped to what's listed in the security section below). In Well, open Connections > Cargo, paste the key, and save. Well validates the key against Cargo's API and pulls a first sample as confirmation.
What does Well pull into the workspace from Cargo?
Well brings in company record, and person record from Cargo and reshapes each entity into your workspace: company record becomes customer; person record becomes contact. Every record arrives with the source identifier preserved, so Cargo stays the source of truth while Well lets you query the data alongside the rest of your stack.
What does Cargo unlock once it is connected to Well?
Once Cargo 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 Cargo source, so you can always trace a workspace record back to the original.
How does Well match a company record from Cargo to a customer in my workspace?
Each Cargo 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 Cargo source attached.
How often does Cargo sync with Well, and what triggers a refresh?
Well polls Cargo regularly for company record and 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 Cargo's side stays modest.
Can I disconnect Cargo and what happens to the data Well already pulled?
Open Connections > Cargo in Well, click Disconnect, then rotate the API key on Cargo's side. Well stops calling Cargo as soon as you disconnect; rotating the key on the provider's side guarantees Well cannot resume access. The company record and person record already synced stay in your workspace until you ask Support to purge them.
How does Well protect what it pulls in from Cargo?
The Cargo records Well holds are encrypted at rest and handled in line with GDPR. See /privacy for the current data-handling policy.
Pairs well with Cargo
More in API
Popular cross-category
Ready to build with the Cargo?
Connect once. Every company record, person record from Cargo becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.