Wealthbox
CRMConnect AI agents to Wealthbox, the CRM built for financial advisors. Agents create contacts, tasks, events, and notes, start workflows against a contact, project, or opportunity, and read the comment history on each record.
What This Integration Enables
Wealthbox is the CRM built for financial advisors, and the thing that separates it from a general sales CRM is that its record of a client relationship is meant to be readable by whoever picks up the phone next. That is why the activity stream matters more here than a pipeline view, and why this connector spends as much of its surface on notes, tasks, events, and workflows as on opportunities. Contacts, tasks, events, opportunities, projects, and workflows are all addressable, and dictionaries populate assignees, categories, pipeline stages, and workflow templates from your own workspace rather than from a fixed list, so a flow writes the category names your firm actually uses.
Two boundaries in this connector are worth stating plainly, because they shape what an agent can be asked to do. Notes can be created and listed but not updated or deleted, since the Wealthbox API exposes create and read for notes and no delete route. Comments are read only. List Comments retrieves them, and there is no create: probing the comments route showed no create path available, so an agent can read what colleagues have said on a record and cannot reply in the thread. That is a meaningful constraint for a flow that wants to keep a conversation inside the CRM, and the honest design response is to have the agent escalate through a channel where a person can answer rather than pretending it can post back. The rest of the mechanics: all calls go to the v1 API on api.crmworkspace.com, and the API access token is sent as the ACCESS_TOKEN request header, created in Wealthbox under Settings, API Access. Wealthbox allows roughly one request per second measured over a five minute window with short bursts tolerated, returning HTTP 429 above that, so bulk operations need to be spaced. List actions page with per_page, defaulting to 25, and page, defaulting to 1, and responses include a meta object carrying the total count and current page. Tasks, events, notes, opportunities, projects, and workflows attach to a parent record through Linked To ID plus Linked To Type, where the type defaults to Contact and also accepts Project and Opportunity where applicable, mapping to the Wealthbox linked_to array. Task categories, event categories, and opportunity stages are workspace specific and come through as dictionaries whose value is the category or stage name, which is what create and update expect. Opportunity Amount, Amount Kind of Projected or Actual, and Currency combine into a single entry in the opportunity amounts array, with currency defaulting to USD and kind to Projected. Task due dates and event times use the Wealthbox display format, for example 2026-02-10 10:00 AM -0500. Create actions accept a Visible To value of Everyone, Private, or a specific user group id. This connector ships no triggers, because Wealthbox does not document a public webhook subscription API, so change detection is a scheduled poll of the list actions, and List Tasks and List Contacts carry an Updated Since filter that makes that poll efficient rather than wasteful. Delete Contact, Delete Task, Delete Event, Delete Opportunity, and Delete Workflow permanently remove the record.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A signed agreement that opens the client record with its history attached
An engagement letter is completed in DocuSign or HelloSign. The agent calls List Contacts to check whether this person is already in the workspace, because an advisory firm that ends up with two records for the same household loses the one thing the CRM is for. Where the client is new, Create Contact writes them with the responsible advisor assigned and Visible To set deliberately rather than left to default. Create Note records what the agreement covered, linked through Linked To ID with a Linked To Type of Contact. Create Task schedules the first review with a due date in the Wealthbox display format, and Create Event books the introductory meeting on the advisor's calendar. The standard onboarding process itself waits for the approval described below.
Conversations that reach the record the next advisor will read
A client emails, calls, or messages. The agent summarises the exchange and calls Create Note against the linked contact so the substance lands in the activity stream rather than in one person's inbox. Where the conversation revealed something that changes the plan, Create Task assigns the follow-up to the right advisor using the workspace assignee dictionary, and Update Opportunity revises the amount with Amount Kind set to Actual rather than Projected once a figure is confirmed. Where colleagues have already discussed the client on the record, List Comments reads that thread so the agent's summary does not repeat what someone has already said. Because this connector cannot create a comment, anything needing a colleague's answer is routed to Slack or Microsoft Teams, where a person can actually reply, with a link back to the Wealthbox record.
A practice review assembled from reads alone
On a schedule the agent calls List Opportunities, List Tasks with the Updated Since filter, and Get Activity Stream, paging with per_page and page and reading meta for the total so a first page is never mistaken for the whole picture. For each open opportunity it joins the linked contact through Get Contact and the scheduled work through List Events, separating opportunities that have a dated task and a booked meeting against them from opportunities that have neither. The result appends to Google Sheets for the practice review, and a per-advisor summary posts to the principal. Because Wealthbox rate limits to roughly one request per second over a five minute window, the run is paced rather than parallelised, which is the correct trade for a report nobody needs in the next ninety seconds.
Human-in-Loop Highlight
Start Workflow is the operation to gate. A Wealthbox workflow is not a status field, it is a template the firm has agreed on, and starting one instantiates the whole thing: a sequence of tasks and steps attached to a client record and assigned to real advisors, appearing on their lists as work the firm has committed to doing. That is exactly what you want when a client genuinely signs, and exactly what you do not want fired speculatively. An agent watching for a signature event can see that a document completed. It cannot see that the same household already has an onboarding workflow running from a previous engagement, that the advisor named in the template dictionary left the firm last month, or that the client asked to delay the account transfer until after a tax filing. Start a client onboarding template on a household that is already halfway through one and you have not created a duplicate record, you have created a duplicate set of obligations, some of which involve contacting the client. The only reverse available here is Delete Workflow, which permanently removes the workflow and cannot be undone, so unwinding a wrong start means destroying the record that it happened at all. So the agent prepares and waits. It calls List Workflows against the client to see what is already running, List Contacts to confirm the household is not duplicated, and the workflow template dictionary to name the exact template it intends, then posts to the responsible advisor: "Engagement letter completed for the Halloran household. Contact exists, created 14 months ago, currently assigned to you. List Workflows shows one workflow already open on this contact, Annual Review, started 3 weeks ago. I would start Client Onboarding, which creates 11 tasks across you, the operations team, and compliance, and books the first two meetings. Starting it does not close the Annual Review workflow, and the only way to remove a workflow started in error is Delete Workflow, which is permanent. Start Client Onboarding, start it after the Annual Review closes, or leave this to you?" The advisor answers once, and Start Workflow runs only where a person released it. This is the human-in-the-loop moment on a CRM built for a regulated advice business, because an agent can prove a document was signed and only an advisor can say whether the firm is ready to make the client eleven new promises.
Agent Capabilities
27 actionsAccount
2- Get Current User Returns the user the configured access token acts as, worth calling once so a flow knows the identity behind its writes.
- Get Activity Stream Reads the workspace activity stream, which is where a practice review sees what has actually been happening across client records.
Contacts
5- List Contacts Returns contacts with `per_page` and `page` paging and a `meta` object carrying the total. Supports an Updated Since filter, which is what makes the scheduled poll that substitutes for events efficient rather than wasteful.
- Get Contact Retrieves a single contact with its assignment, tags, and details.
- Create Contact Creates a client or prospect contact with the responsible advisor assigned and a Visible To value of `Everyone`, `Private`, or a specific user group id.
- Update Contact Updates a contact, used to keep a client record current from the system that owns the field.
- Delete Contact Permanently removes a contact and cannot be undone.
Tasks
4- List Tasks Returns tasks with paging and an Updated Since filter, used to see what work is genuinely scheduled against a client.
- Create Task Creates a task linked to a parent through Linked To ID and Linked To Type, with a due date in the Wealthbox display format such as `2026-02-10 10:00 AM -0500` and a category drawn from your workspace dictionary.
- Update Task Updates a task, including its due date, category, and assignee.
- Delete Task Permanently removes a task and cannot be undone.
Events
4- List Events Returns calendar events with paging, used to see what is actually booked with a client.
- Create Event Books a calendar event linked to a contact, project, or opportunity, with start and end times in the Wealthbox display format and a workspace event category.
- Update Event Updates an event, including rescheduling it.
- Delete Event Permanently removes an event and cannot be undone.
Notes
2- List Notes Returns the notes recorded against records, used to read what the team already knows before adding to it.
- Create Note Writes a note against a linked record, which is how a call summary or an inbound message reaches the activity stream the whole team reads. Notes cannot be updated or deleted through the API, so a note is written once.
Opportunities
4- List Opportunities Returns opportunities with paging, used for pipeline reporting across the practice.
- Create Opportunity Creates an opportunity against a linked record. Amount, Amount Kind of Projected or Actual, and Currency combine into a single entry in the `amounts` array, with currency defaulting to USD and kind to Projected.
- Update Opportunity Updates an opportunity, including moving it to a workspace-defined stage and revising the amount from Projected to Actual.
- Delete Opportunity Permanently removes an opportunity and cannot be undone.
Projects
2- List Projects Returns projects, which act as a parent record that tasks, events, and notes can be linked to.
- Create Project Creates a project, used to group the work around a client engagement that spans more than a single meeting.
Workflows
3- List Workflows Returns the workflows currently running, and the read that has to happen before another is started against the same client.
- Start Workflow Instantiates a workflow template against a linked record, creating the sequence of tasks and steps the firm has standardised. Templates come from your workspace dictionary.
- Delete Workflow Permanently removes a workflow and cannot be undone, which is the only reverse available for a workflow started in error.
Comments
1- List Comments Reads the comments colleagues have left on records. Comments are read only through this connector, since the Wealthbox API exposes no create route for them, so an agent can read a thread and has to escalate elsewhere to answer it.
Frequently Asked Questions
What can FlowRunner do with Wealthbox?
FlowRunner agents can run Get Current User, Get Activity Stream, and List Contacts in Wealthbox, plus 24 more actions.
Does connecting Wealthbox to FlowRunner require OAuth?
No. Wealthbox connects to FlowRunner with an API key, no OAuth flow required.
Can Wealthbox trigger a FlowRunner workflow automatically?
Wealthbox doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Wealthbox
$100 in credits. No card required. Connect in minutes.