CRM & Sales · Integration
Wealthbox
Add Wealthbox to your product for your customers, and give your AI agents governed access to it.
Wealthbox serves its API from api.crmworkspace.com/v1 rather than from wealthbox.com, which is the first thing that stalls a new integration. Authentication uses an ACCESS_TOKEN header carrying a key generated by an individual advisor, so what you can read is that user's visibility inside the firm rather than the firm's entire book. Contacts come in three kinds, person, household and organisation, and households link their members together, so a naive contact sync creates duplicates unless household membership is respected. Around contacts sit opportunities, tasks, events, notes and workflows, and custom fields are defined per firm, so field definitions have to be read before anything is mapped into them. fastn holds each advisor's Wealthbox key in its own tenant and keeps the field mapping current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Wealthbox account so client records in your product stay aligned with their CRM
Create tasks and notes against the right contact when an event happens in your app
Respect household structure when syncing so spouses and dependants are not written as separate unlinked contacts
Read opportunities and their stages to report pipeline inside your own dashboards
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent log a note or complete a task against a named contact, with the contact ID and advisor key recorded per tenant
Have an agent find contacts missing household links or required custom fields and list them for correction
Let an agent prepare a meeting brief from a contact's notes, tasks and upcoming events without editing anything
Example prompt
Which Wealthbox households have a review meeting due and no note logged in the last six months?
Set up Wealthbox in 4 steps
- 01Enable the Wealthbox connector from your fastn dashboard.
- 02Have each customer authorise their own Wealthbox account, so calls run under their credentials rather than a shared key.
- 03Decide which accounts, contacts and opportunities your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Wealthbox integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Wealthbox integration without building it. Your customers connect their own Wealthbox account inside your product and work their accounts, contacts and opportunities there, with no per-customer code on your side.
- Handle the part that actually costs time: every CRM instance is customised, so standard objects are never the whole story. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Wealthbox update is not your on-call problem.
- One integration serves your product and your agents. The same governed Wealthbox connection powers in-product features and gives AI agents scoped, audited access, so you keep customer records aligned between your product and the CRM each customer already runs without wiring it twice.
Used by these teams
Compare with
Salesforce
HubSpot
PipedriveOften used alongside
Tools the same teams tend to run next to Wealthbox, across other categories.
Slack
Mailchimp
Marketo
Google AdsWealthbox integration FAQ
How do I add a Wealthbox integration to my product?
Enable the Wealthbox connector in your fastn dashboard, then let each customer authenticate their own Wealthbox account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Wealthbox client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Wealthbox account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Wealthbox account and only ever sees their own accounts, contacts and opportunities. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Wealthbox integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent log a note or complete a task against a named contact, with the contact ID and advisor key recorded per tenant
Who maintains the Wealthbox integration?
fastn does. When Wealthbox changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Wealthbox integration support custom fields and custom objects?
Yes. CRM instances are heavily customised, so field and object mapping is configuration rather than code. Each customer maps their own fields during setup, which means onboarding a customer with an unusual Wealthbox schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Wealthbox, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Wealthbox do not drift apart.
What can I build with the Wealthbox integration?
A common starting point: let a customer connect their own Wealthbox account so client records in your product stay aligned with their CRM. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Wealthbox integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Wealthbox does not change your per-connector cost. You can start free with 3 connected accounts.
Add Wealthbox to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.