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