Help center
How Worthune works with your systems
Worthune keeps one current record per client household and sits beside the systems you already use. These guides explain, in plain English, how a book comes in, how it stays current, how your CRM and portfolio system fit, what comes back out, and what is stored. No developer needed to read them.
For the exact calls behind each step, the developer docs are the reference.
Last reviewed
How integration works
One household record, three ways data comes in, and what comes back out.
Read the guide →Bringing your book in
Export, map once, dry run, import. Nothing is written until the dry run is clean.
Read the guide →Keeping households current
Small updates from your feeds, versioned so nothing is overwritten by accident.
Read the guide →Connecting your CRM and portfolio system
Your identifiers stay yours; Worthune keeps the household in step with them.
Read the guide →Getting data out
Notifications on every change, a client picture on demand, and a full history you can export.
Read the guide →What Worthune stores, and what it never holds
Balances by account, birth years and relationships. Not holdings, not transactions, not names.
Read the guide →Getting and using a sandbox key
A free key by email, thirty days, the whole platform within limits.
Read the guide →Questions
Common questions
- Who is the help center for?
- Operations, integration and product staff at a customer, and anyone evaluating Worthune who is not a developer. It explains what happens and in what order; the developer docs carry the exact calls.
- Where are the developer docs?
- At worthune.com/docs: the REST quickstart, the SDKs, the MCP server, and the full household engine reference.
- How do I get help with something not covered here?
- Write to support@worthune.com. Launch includes email support; Growth includes priority support with a named contact.