Integration Products | Campaign Creators

Jack Henry HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 19, 2026, 6:38:08 AM
Integration Assessment
Integration Assessment · Banking & Lending

Jack Henry × HubSpot

How a bank on SilverLake, CIF 20/20 or Core Director, or a credit union on Symitar, can bring customers, members and the products they hold into HubSpot for onboarding and cross-sell journeys, without moving account numbers or balances out of the core.

SilverLake · CIF 20/20 · Core DirectorSymitarjXchange (SOAP)SymXchange (SOAP)Banno Digital ToolkitData minimization by design
Platform ownerJack Henry & Associates
Integration typeCustom, core APIs plus nightly batch
Primary directionJack Henry → HubSpot
FeasibilityBuildable, access via the institution
API accessOpen with conditions
01 — Summary

Does Jack Henry integrate with HubSpot?

The Jack Henry core is the system of record for every customer or member and every deposit, loan and card they hold. HubSpot is where marketing and service act on that relationship. This assessment shows how to connect them with the least data necessary.

API access
Open APIOpen with conditionsGated API

Public documentation, but production access needs vendor approval, certification, a paid license or a specific plan.

Open with conditions. jXchange and SymXchange are documented on Jack Henry's developer site, with a sandbox. Production access is set up per institution through Jack Henry's developer programs.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

The core knows what each member holds; HubSpot turns that into the next conversation.

Campaign Creators assessment

Jack Henry exposes its bank cores through jXchange, a native SOAP interface with XML payloads and a REST translation layer, and its Symitar credit union core through SymXchange, a SOAP web service over account, share, loan and name records. Both are documented on Jack Henry's developer site and come with a sandbox for development. Jack Henry also lists bulk data (Operational Data Integration) and event streaming (Enterprise Event System) for institutions that use them. That makes a HubSpot integration buildable. Two things set the pace: production credentials are issued per institution through Jack Henry, and the institution's compliance team decides which customer data HubSpot may hold.

Scorecard
Data richnessHigh
API accessVia institution
Public docsGood
Build complexityMod–High

Ratings are CC judgments from Jack Henry's public developer documentation and product materials. Which interfaces an institution has licensed, and their limits, are confirmed with the institution and Jack Henry in discovery.

Strength

Documented core APIs with a sandbox

jXchange and SymXchange are documented publicly, and Jack Henry's Vendor Integration Program provides a development environment with a test database of customer and member accounts.

Plan for

Holdings, not account numbers

HubSpot needs to know that a member has an auto loan or a CD maturing soon. It does not need the account number or balance. The integration sends product flags, dates and counts by default.

Gate

Institution credentials and compliance

Production access is set up per institution, often with its own key pair. The compliance team approves the field list, treating GLBA as a planning item, before any build starts.

02 — API modules

Which Jack Henry APIs does the integration use?

Seven Jack Henry interfaces and data sources are relevant to HubSpot. Three carry the integration, three extend it where the institution has them, and one is a scope decision.

Core

jXchange

SilverLake · CIF 20/20 · Core Director

Jack Henry's native SOAP interface to its bank cores, with XML payloads and a REST translation layer that maps XML to JSON.

  • Customer and account inquiries
  • OAuth 2.0 tokens from a key pair
  • Shared DMZ sandbox for development
Core

SymXchange

Symitar · credit union core

A SOAP web service over the Symitar database: accounts with their share, loan, name and card records.

  • getAccountSelectFields for only the fields needed
  • Share and loan records give product holdings
  • PowerOn specfiles for custom extracts
Batch

Nightly batch data

Operational Data Integration · core extracts

Full holdings for every customer or member, delivered once a day. Jack Henry lists Operational Data Integration for bulk data; Symitar institutions can also produce an extract with a PowerOn specfile.

  • The main source for rollups
  • Avoids a core call per customer
  • Confirm the method each institution uses
Real time

Enterprise Event System

Event streaming

Event streaming from Jack Henry systems, for changes HubSpot should act on the same day, such as a new account.

  • Account opened and closed signals
  • Reduces polling between nightly runs
  • Confirm events available to the institution
Engagement

Banno Digital Toolkit

Digital banking · APIs, plugins, SSO

Banno is Jack Henry's digital banking platform. Its toolkit offers APIs, plugins and an authentication framework.

  • Digital banking enrollment
  • Last digital login, where available
  • Confirm institution-level data access
Plan ahead

Jack Henry Platform

Cloud-native modules · Digital Core APIs

Cloud-native core modules connected to the existing core, which stays the system of record. Digital Core has its own API documentation.

  • Same HubSpot data model applies
  • Adds API options as modules are adopted
  • Review at each core change
Scope decision

Account numbers, balances and transactions

Scope decision

Off by default. Balance bands or masked numbers are added only when the compliance team approves a specific use.

  • Product flags and dates instead of numbers
  • Balance bands, not balances, if approved
  • Transaction detail stays in the core
03 — Framework

How does the Jack Henry HubSpot integration work?

A nightly batch carries full product holdings, and core APIs or events carry same-day changes. A CC-built integration layer matches each customer or member to a HubSpot contact, turns account records into product flags and dates, drops restricted fields, and writes in batches.

Jack Henry
jXchangebank cores: customers, accounts
SymXchangeSymitar: accounts, shares, loans, names
Nightly extractfull holdings, all customers
Bannodigital banking engagement
CC integration layer
Secure intakeSOAP calls and nightly file pickup
Core sync moduleone per core type
Identity resolverhashed core key · email
Data minimizerflags, dates, counts; drops numbers
HubSpot writerbatch upserts, error replay
HubSpot
Contactscustomers and members
Companiesbusinesses and households
Product holdings (custom object)product type, status, open date
Custom eventsaccount opened, loan paid off
Lists, workflows & reportsonboarding, life events, cross-sell
Jack Henry → HubSpot (primary flow)HubSpot → Jack Henry (contact preferences, only where approved)
Principle

The core stays the system of record

Accounts, balances and identity verification live in the core. HubSpot holds the relationship view that marketing and service act on.

Principle

Send the least data that works

Every field must support a named journey. Product flags, dates and counts by default; account numbers and balances only with written approval.

Principle

Batch for breadth, real time for moments

The nightly run keeps every record complete. API calls and events are reserved for changes that need a same-day response.

04 — Process

What does Jack Henry HubSpot integration setup involve?

Each phase ends on a gate the institution signs off before the next begins. Onboarding journeys usually go live first, then cross-sell and life events.

1

Core and journey inventory

Confirm the core (SilverLake, CIF 20/20, Core Director or Symitar), the interfaces the institution licenses, and the journeys marketing and service want to run from HubSpot.

Gate to next phaseSigned list of journeys and interfaces
2

Access and vendor review

Request jXchange or SymXchange access through the institution and Jack Henry, set up the key pair or credentials, and complete the institution's vendor due diligence on the integration layer.

Gate to next phaseSandbox calls working; production request submitted
3

Compliance and data minimization

Agree the field list, the identity key, how product types map to flags, and whether any balance band or masked number is allowed. GLBA and privacy notices are reviewed by the institution's compliance team.

Gate to next phaseSigned field list and data handling rules
4

HubSpot data model

Create the Product Holdings custom object, contact rollups, custom events, owner mapping and property groups in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build

Build the nightly batch first, then the same-day API or event path, with idempotent writes and an error replay queue.

Gate to next phaseNightly run completes in sandbox with clean reconciliation
6

Backfill

Load every active customer or member and their current holdings, then compute rollups once so lists and reports start complete.

Gate to next phaseHubSpot counts reconcile to core reports within an agreed tolerance
7

Journeys, parallel run & launch

Build onboarding, life-event and cross-sell workflows with sends paused, run two weeks in parallel, then switch on.

Gate to next phaseFive consecutive nightly runs with no unresolved errors
05 — Data mapping

What does the Jack Henry HubSpot integration sync?

Field names describe core data as Jack Henry's public documentation presents it. Symitar record types come from the SymXchange documentation. Exact element names for each core are confirmed against the jXchange or SymXchange specification in discovery.

Jack Henry fieldHubSpot propertyObjectDirectionNotes
Customer or member · contact record
Customer ID (bank) or person record (Symitar)jh_core_keyContactJH → HSOne-way hash of the core key. Unique. Never the account number.
First and last namefirstname, lastnameContactJH → HSCore is the source; HubSpot edits stay in HubSpot.
Email addressemailContactJH → HSMatch key alongside the hashed core key.
Phonephone, mobilephoneContactJH → HSSMS needs separate consent.
City, state, ZIPcity, state, zipContactJH → HSStreet address kept out unless approved.
Relationship start datejh_customer_sinceContactJH → HSTenure for segmentation.
Age bandjh_age_bandContactJH → HSComputed from date of birth in the integration layer. Date of birth is not stored.
Ownership and organization
Primary officerhubspot_owner_idContactJH → HSOfficer code matched to a HubSpot user.
Branchjh_branchContactJH → HSDrives branch views and routing.
Business customername, jh_core_keyCompanyJH → HSBusiness and its signers associated as contacts.
HouseholdHousehold (company)CompanyJH → HSOnly where the core or institution defines households.
Product holdings · custom object
Account (bank) or share / loan record (Symitar)Product HoldingCustom objectJH → HSOne record per product. No account number.
Product typejh_product_typeProduct HoldingJH → HSChecking, savings, CD, loan, card, mortgage.
Product code and descriptionjh_product_codeProduct HoldingJH → HSInstitution's own product codes.
Open datejh_open_dateProduct HoldingJH → HSStarts onboarding timing.
Statusjh_statusProduct HoldingJH → HSOpen, closed, paid off.
Maturity date (CDs and loans)jh_maturity_dateProduct HoldingJH → HSDrives renewal and refinance journeys.
Balancejh_balance_bandProduct HoldingJH → HSOff by default. Band only, if compliance approves.
Rollups and life events
Products heldjh_products_heldContactJH → HSMulti-select rolled up from holdings.
Product countjh_product_countContactJH → HSRelationship depth.
New account openedCustom event: Account openedContactJH → HSNightly or same day through events.
Loan paid offCustom event: Loan paid offContactJH → HSTrigger for the next lending offer.
Address changedCustom event: Address changedContactJH → HSMoving signal for mortgage and service outreach.
Digital banking enrolledjh_digital_enrolledContactJH → HSFrom Banno, where available.
Last digital loginjh_last_digital_loginContactJH → HSFrom Banno. Confirm availability in discovery.
HubSpot to core
Marketing email opt-outCustomer preference fieldCoreHS → JHOnly where the institution wants the core to hold it. Confirm field in discovery.
Referral from HubSpotOfficer task or referral recordCoreHS → JHOpt-in scope. Many institutions keep referrals in HubSpot.
06 — Auth & API

How are authentication and API limits handled?

Jack Henry documents its core interfaces publicly; production access is set up per institution. Values Jack Henry does not publish are marked for confirmation.

TopicJack HenryHubSpot
Access modelThrough the institution's Jack Henry relationship and Jack Henry's developer programs (Vendor Integration Program; Fintech Integration Network). Development uses Jack Henry's sandbox.Self-serve in the client portal. Custom objects and custom events need an Enterprise hub.
InterfacesjXchange: native SOAP with XML payloads, plus a REST translation layer. SymXchange: SOAP web service. Bulk data and event streaming listed on the developer site.REST APIs: CRM objects, associations, custom events, imports.
AuthenticationjXchange: OAuth 2.0 client credentials using a public/private key pair; tokens last 10 minutes; production may need a key pair per institution. SymXchange: credentials or a token carried in each request.Private app access token or OAuth 2.0 public app, scoped per object.
Real time vs batchAPIs answer per customer or account. Full holdings for every customer come from a nightly batch. Event streaming adds same-day signals where licensed.Writes are immediate; batch endpoints handle nightly volume.
EnvironmentsjXchange DMZ sandbox (no real personal data), then test or UAT, then the institution's production. SymXchange development against a test database.HubSpot sandbox for build and parallel run.
Rate limitsNot published. Confirm with Jack Henry and the institution.Per-10-second burst and daily limits by subscription tier.
Sensitive dataAccount numbers, balances, transactions, tax IDs, dates of birth. The integration hashes the core key and drops restricted fields.Sensitive data properties available on Enterprise; field-level permissions by team.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Customer data needs compliance sign-offHigh

Core data is nonpublic personal information under GLBA. The institution's compliance team decides what HubSpot may hold and how privacy notices apply. CC builds to that decision and documents it in the SOW.

Production access runs through the institutionHigh

Credentials are issued for each institution and may need their own key pair. Make access and vendor due diligence client-owned dependencies, with dates.

Symitar member numbers are account numbersMedium

On Symitar the member account number identifies the member. Store a one-way hash as the HubSpot key, never the number itself.

Nightly timingMedium

Core processing runs overnight, so most data is a day old. Journeys that need same-day action use events or API calls, and the SOW says which ones.

Product code mappingMedium

Each institution has its own product codes. Map them to HubSpot product types in a table the institution owns and updates.

Core changesLow

Moving modules to Jack Henry Platform or changing cores changes the interfaces. Keep the core sync module separate so the HubSpot model does not change.

Opportunities in HubSpot

New account onboardingHigh value

Every new checking account, loan or card starts a timed onboarding journey in HubSpot: welcome, digital banking enrollment, direct deposit, next product.

Cross-sell from real holdingsHigh value

Members with a checking account and no credit card, or an auto loan and no savings, enter targeted lists automatically each night.

Life-event journeysHigh value

CD maturities, loan payoffs and address changes become prompts for renewal, refinance and mortgage conversations.

Digital banking adoptionMedium value

Banno enrollment status shows which members still need help going digital, and HubSpot follows up until they enroll.

Branch and officer ownershipMedium value

Each contact is owned by the right officer and branch, so tasks, sequences and reports follow the real relationship.

Relationship reportingMedium value

Product depth, tenure and journey results by branch and segment in HubSpot dashboards, without exporting core reports.

Rollout order

Start with onboarding, then grow the relationship.

Every phase uses the same HubSpot data model, so value arrives in steps. Each step adds a journey, not a new data source.

  1. Nightly batch of customers or members and product flags, matched to HubSpot contacts.
  2. Onboarding journeys for every new account, loan and card.
  3. Cross-sell and life-event journeys from holdings, maturities and payoffs.
  4. Same-day events and Banno engagement, once the nightly model is stable.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the jh_ prefix in a Jack Henry property group. Nothing in this schema holds an account number, balance, tax ID or date of birth.

Internal nameLabelObjectTypeSource / logic
jh_core_keyCore Key (hashed)ContactSingle-line textOne-way hash of customer ID or member record; unique
jh_customer_sinceCustomer SinceContactDate pickerRelationship start date
jh_age_bandAge BandContactDropdownComputed in the integration layer
jh_branchBranchContactDropdownPrimary branch
jh_products_heldProducts HeldContactMultiple checkboxesRollup of open product types
jh_product_countProduct CountContactNumberCount of open products
jh_digital_enrolledDigital Banking EnrolledContactSingle checkboxFrom Banno, where available
jh_product_typeProduct TypeProduct HoldingDropdownMapped from institution product codes
jh_product_codeProduct CodeProduct HoldingSingle-line textInstitution's product code
jh_open_dateOpen DateProduct HoldingDate pickerFrom the core account record
jh_statusStatusProduct HoldingDropdownOpen, closed, paid off
jh_maturity_dateMaturity DateProduct HoldingDate pickerCDs and term loans
09 — Scope builder

Interactive scope builder

Choose the data and journeys for this engagement and the direction each field syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
Jack Henry × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Jack Henry HubSpot integration FAQ

Does Jack Henry integrate with HubSpot?

Yes, but access is open with conditions: Jack Henry publishes jXchange and SymXchange documentation with a sandbox, but production access is issued per institution through Jack Henry's developer programs once that institution's agreement is in place. Campaign Creators builds a custom integration layer on those core APIs plus the nightly Operational Data Integration batch.

What data syncs between Jack Henry and HubSpot?

Customers and members sync into HubSpot contacts and companies, and their product holdings (checking, savings, loans, cards, CDs) sync into a Product Holding custom object with open date, status and maturity date, plus custom events such as account opened or loan paid off. HubSpot writes back only limited, opt-in items such as marketing preferences, never account numbers or balances.

Which system owns which data?

The Jack Henry core stays the system of record for account numbers, balances, transactions and identity verification, and HubSpot never edits an account or core record. HubSpot owns the relationship and marketing view: product flags, dates, tenure and journey activity, with account numbers, balances, tax IDs and dates of birth excluded by default.

What does setting up the Jack Henry HubSpot integration involve?

Seven phases, each closed by an institution sign-off: a core and journey inventory, requesting jXchange or SymXchange access and completing vendor due diligence, a compliance and data-minimization review of the field list, the HubSpot data model with a Product Holdings custom object, the build of the nightly batch and same-day event path, a backfill and reconciliation of every customer or member, and a two-week parallel run before onboarding and cross-sell journeys go live.

How long does the integration take and what does it cost?

Timeline and cost depend on which core (SilverLake, CIF 20/20, Core Director or Symitar) and interfaces the institution has licensed, the journeys marketing and service want to run, and how much compliance review the field list requires. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.