Back to integrations
CRM Integration
Policy Balance Hub for Salesforce
Live API sync via OAuth — read-only, every 15 minutes
Connect your Salesforce org through the standard OAuth flow — you authorise it in Salesforce, and Policy Balance Hub never sees a password. From then on it reads your contacts and opportunities on a schedule, pulling only what changed. Nothing is written back to Salesforce.
Plan availability: CRM connections are available on Professional and up, where contacts sync into clients. Opportunities import into leads, which is on the Agency plan and up: on Professional they are not imported at all, and moving to Agency backfills the opportunities that were skipped.
What the integration does
- Standard OAuth connect flow — authorise in Salesforce, no credentials typed into Policy Balance Hub
- Contacts become clients, carrying name, account name, email, phone and mailing address
- On the Agency plan, opportunities become leads, with the opportunity amount kept as estimated premium. On Professional the sync does not import them
- Renamed stages still map correctly: an unrecognised stage name falls back to the org's own IsWon and IsClosed flags before defaulting to a new lead
- Incremental by SOQL — each run asks Salesforce only for records modified since the last watermark, rather than re-reading the org and burning your daily API allocation
- A field-coverage report shows which Salesforce field fills which Policy Balance Hub field before you sync anything, and Test connection reports per-object read access
Why agencies use it
- Keep one client list current across Salesforce and reconciliation without an export step
- Use the OAuth flow your Salesforce admin already knows, rather than issuing anyone a standing credential
- Know what the sync will and will not fill before you turn it on
What it does not do
Stated up front rather than discovered later.
- Read-only. Nothing is written back to Salesforce, and there is no two-way sync.
- Contacts and opportunities only. Accounts, leads, cases, tasks and custom objects are not read as objects in their own right — an account's name arrives only as the contact's business name.
- Salesforce is the source of truth for the fields it fills. Editing one of those fields in Policy Balance Hub is overwritten on the next sync.
- Records are matched on the Salesforce record ID, so a client you already created by hand arrives as a separate record rather than being merged into the existing one.
- A full state name in MailingState is dropped rather than truncated to two characters, because a wrong two-letter code is worse than a blank one.
- On Professional, opportunities are not imported at all. Leads are an Agency-plan feature, so the sync reads your opportunities and then skips them rather than writing records your plan does not include. Upgrading to Agency backfills them: the next sync re-reads your whole org and imports the opportunities it skipped.
Frequently asked questions
- Does Policy Balance Hub write anything back to Salesforce?
- No. The connector is inbound only. It reads contacts and opportunities and has no write path — your Salesforce org stays the system of record and is never modified by the sync.
- Which plan do I need, and what happens to my opportunities on Professional?
- The connection itself is on Professional and up, and on Professional the contact-to-client half works fully. Opportunities are the half that depends on your plan: they import into leads, leads are an Agency-plan feature, and so on Professional the sync does not import them at all. It reads your opportunities, skips them, and the connection card in the app says it is doing that — nothing is written into a workspace your plan does not include. Move to Agency and the next scheduled sync re-reads your whole org and backfills the opportunities it skipped, so the months you spent on Professional are not a gap in your lead history. If leads are the reason you want the sync, budget for Agency.
- We renamed all our opportunity stages. Will the mapping still work?
- Yes. The connector checks the stage name first, and when it does not recognise one it falls back to the IsWon and IsClosed flags that every org has regardless of how stages are named — a closed-won opportunity arrives as a bound lead, a closed-lost one as lost. Anything still open becomes a new lead rather than being dropped.
- How are our credentials stored?
- The OAuth refresh token is held encrypted at rest and is never returned by any API response. A fresh access token is derived from it at the start of every sync run and lives only in memory for that run. Disconnecting the org deletes the stored credential.
Ready to stop drowning in spreadsheets?
See how Policy Balance Hub can automate premium reconciliation for your agency. Start the trial in minutes — or request a personalized walkthrough.
14-day free trial (up to 100 policies, 3 users). No credit card required.