Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Wealthbox

Wealthbox integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Wealthbox with Flows360

Wealthbox integration for Flows360 workflows.

Use the Wealthbox connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 11 actions and 4 triggers.

Available actions

  • Create Contact
  • Create Note
  • Create Project
  • Add Member to Household
  • Create Household
  • Create Event
  • Create Opportunity
  • Create Task
  • Plus 3 additional declared actions.

Available triggers

  • New Task
  • New Contact
  • New Event
  • New Opportunity

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Wealthbox
  • Package: @activepieces/piece-wealthbox@0.1.6
  • Exact artifact digest: sha256:8256591672ee19804c753a23b844ae07d1536302d0b84a4a439184ea654053f8
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Contact (create_contact), Adds a new contact with rich details (name, address, email, tags, etc.) Classification: read.
  • Create Note (create_note), Adds a note linked to a contact. Log call summaries against client records. Classification: read.
  • Create Project (create_project), Starts a new project with description and organizer. Launch project-based onboarding when new clients sign up. Classification: read.
  • Add Member to Household (add_household_member), Adds a member to an existing household. Link multiple contacts under one family unit. Classification: read.
  • Create Household (create_household), Creates a household record with emails, tags. Group family member contacts into one household. Classification: read.
  • Create Event (create_event), Creates a calendar event linked to contact. Schedule advisory meetings on behalf of clients. Classification: read.
  • Create Opportunity (create_opportunity), Logs an opportunity including stage, close date, amount. Automate opportunity tracking after meetings. Classification: read.
  • Create Task (create_task), Creates tasks tied to contacts with due dates and assignment types. Assign follow-up actions when opportunities are created. Classification: read.
  • Start Workflow (start_workflow), Triggers a workflow template on a contact/project/opportunity. Automate multi-step sequences based on CRM events. Classification: read.
  • Find Contact (find_contact), Locate a contact by name, email, phone, or advanced filters. Comprehensive contact search with dynamic filtering options. Classification: read.
  • Find Task (find_task), Finds existing tasks using comprehensive search filters. Search by assignment, resource, completion status, and date ranges. Classification: read.

Trigger contracts

  • New Task, polling.
  • New Contact, polling.
  • New Event, polling.
  • New Opportunity, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects15
Supported actionsNot published
Triggers4

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Access Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Contact Yes No Adds a new contact with rich details (name, address, email, tags, etc.)
Create Note Yes No Adds a note linked to a contact. Log call summaries against client records.
Create Project Yes No Starts a new project with description and organizer. Launch project-based onboarding when new clients sign up.
Add Member to Household Yes No Adds a member to an existing household. Link multiple contacts under one family unit.
Create Household Yes No Creates a household record with emails, tags. Group family member contacts into one household.
Create Event Yes No Creates a calendar event linked to contact. Schedule advisory meetings on behalf of clients.
Create Opportunity Yes No Logs an opportunity including stage, close date, amount. Automate opportunity tracking after meetings.
Create Task Yes No Creates tasks tied to contacts with due dates and assignment types. Assign follow-up actions when opportunities are created.
Start Workflow Yes No Triggers a workflow template on a contact/project/opportunity. Automate multi-step sequences based on CRM events.
Find Contact Yes No Locate a contact by name, email, phone, or advanced filters. Comprehensive contact search with dynamic filtering options.
Find Task Yes No Finds existing tasks using comprehensive search filters. Search by assignment, resource, completion status, and date ranges.
New Task Yes No polling trigger declared by the pinned package.
New Contact Yes No polling trigger declared by the pinned package.
New Event Yes No polling trigger declared by the pinned package.
New Opportunity Yes No polling trigger declared by the pinned package.

Triggers

New Task · Poll

Fires when a new task is created

Inputs

  • assigned_to · string
  • assigned_to_team · number
  • created_by · string
  • task_type · string
  • resource_type · string
  • resource_record · object
New Contact · Poll

Fires when a new contact is created

Inputs

  • contact_type · string
  • type · string
  • household_title · string
  • assigned_to · string
  • tags_filter · array
  • active · string
  • include_deleted · boolean
New Event · Poll

Fires when a new event is created

Inputs

  • resource_type · string
  • resource_record · object
  • event_category · string
  • start_date_min · string
  • start_date_max · string
  • order · string
New Opportunity · Poll

Fires when a new opportunity is created

Inputs

  • resource_type · string
  • resource_record · object
  • stage · string
  • manager · string
  • include_closed · boolean
  • min_probability · number
  • max_probability · number
  • target_close_after · string
  • target_close_before · string

Setup

Setup

  1. Add the Wealthbox connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-wealthbox@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 11 actions and 4 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Wealthbox connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-wealthbox@0.1.6 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com