Node reference
Wealthbox
Wealthbox node reference - all 49 operations, the credential it needs, and a worked example.
Wealthbox CRM for financial advisors. 49 operations: contacts and households; tasks; calendar events; notes; opportunities; projects; workflows, workflow templates and workflow steps; the activity stream and comments; and the user, team, tag, custom-field, contact-role and category lookups.
Credential: Wealthbox ACCESS_TOKEN - see Credentials.
Wealthbox has no per-operation grants. The credential this node holds is a personal API access token, created under Wealthbox's own settings by giving it a name and nothing else — there is no checkbox list, no consent screen, and no scope attached to the token at all. What it can reach is simply whatever the Wealthbox USER who created it can reach in that workspace, so the way to limit blast radius is to issue the token under a restricted user rather than to narrow the token. Wealthbox does publish two coarse OAuth 2.0 scopes, login and data, for partner integrations authenticating through app.crmworkspace.com/oauth/authorize — but that flow is not what this node uses, and Wealthbox's API reference never maps a single endpoint to either scope, so there is no honest per-operation table to state. Read the errors accordingly: a 401 means the token is wrong or revoked; a 403 means the token's owner cannot see that record, most often because it was saved with visible_to set to Private or to a user group they are not in; and a 429 is the rate limit (about one request per second over a five-minute window) rather than a permission at all.
| Operation | What it does |
|---|
createContact | Create contact |
getContact | Get contact |
updateContact | Update contact |
listContacts | List / search contacts |
deleteContact | Delete contact |
| Operation | What it does |
|---|
addHouseholdMember | Add contact to a household |
removeHouseholdMember | Remove contact from a household |
| Operation | What it does |
|---|
createTask | Create task |
getTask | Get task |
updateTask | Update / complete task |
listTasks | List tasks |
deleteTask | Delete task |
| Operation | What it does |
|---|
createEvent | Create calendar event |
getEvent | Get event |
updateEvent | Update event |
listEvents | List events |
deleteEvent | Delete event |
| Operation | What it does |
|---|
createNote | Create note |
getNote | Get note |
updateNote | Update note |
listNotes | List notes |
| Operation | What it does |
|---|
createOpportunity | Create opportunity |
getOpportunity | Get opportunity |
updateOpportunity | Update opportunity |
listOpportunities | List opportunities |
deleteOpportunity | Delete opportunity |
| Operation | What it does |
|---|
createProject | Create project |
getProject | Get project |
updateProject | Update project |
listProjects | List projects |
deleteProject | Delete project |
| Operation | What it does |
|---|
startWorkflow | Start workflow from a template |
getWorkflow | Get workflow |
listWorkflows | List workflows |
deleteWorkflow | Delete workflow |
listWorkflowTemplates | List workflow templates |
getWorkflowTemplate | Get workflow template |
completeWorkflowStep | Complete a workflow step |
revertWorkflowStep | Revert a workflow step |
| Operation | What it does |
|---|
listActivity | List activity stream |
listComments | List comments on a record |
| Operation | What it does |
|---|
getMe | Get my login profile |
listUsers | List users |
listTeams | List teams |
listUserGroups | List user groups |
listTags | List tags |
listCustomFields | List custom field definitions |
listContactRoles | List contact roles |
listCategoryMembers | List members of a category |
Create a contact that is not a Person
The old node hardcoded type: "Person" on every create, so a Household, Organization or Trust — half of what a wealth-management CRM holds — was simply unreachable. contactKind now exposes it and still defaults to Person, so nothing saved changed meaning.
Set Operation to createContact, then fill in:
| Field | Value | Notes |
|---|
contactKind | Household | Person (the default), Household, Organization or Trust |
bodyJson | {"name": "{{ myTrigger.familyName }} Family"} | Wealthbox's own field names for the chosen kind |
Sets {{household.id}} and {{household.contact}}. Wealthbox allows roughly one request per second averaged over five minutes and sends no rate-limit headers, so a Loop needs a Delay.