A HubSpot Elite Solutions Partner built to help organizations unify strategy, systems, and execution. We design HubSpot systems that scale.

See how we've solved complex HubSpot challenges across migrations, integrations, CMS, automation, and optimization.

Join a team building smarter HubSpot systems. We value strategic thinkers who move proactively, care about quality, and want to do meaningful work.

Integration

HubSpot <> Databricks Integration

Powered by Commercient
HubSpot and Databricks integration
Integration Assessment
Integration Assessment · Data Warehouse

Databricks × HubSpot

How a Databricks lakehouse and HubSpot can exchange data in both directions: HubSpot's CRM records, engagements and marketing activity landing in Delta tables for analysis, and the scores, product usage and lifetime value the data team computes flowing back to the HubSpot records that sales, marketing and service act on.

SQL Statement Execution APIJobs API and triggersDelta Lake Change Data FeedUnity Catalog governanceOAuth M2M service principalsBoth directions
Platform ownerDatabricks
Integration typeHubSpot connector plus custom build on Databricks REST APIs
Primary directionBoth: Delta ↔ HubSpot
FeasibilityStrong fit
API accessOpen API
01 — Summary

Does Databricks integrate with HubSpot?

Databricks is where many data teams join product, billing, support and web data into one model of the customer. HubSpot is where marketing, sales and service act on that customer. This assessment covers how the two share data.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. The REST APIs are documented publicly. A workspace or account admin creates the service principal.

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

Databricks runs SQL, jobs and governance through documented REST APIs, so HubSpot can act on what the lakehouse knows, and the lakehouse can see everything HubSpot records.

Campaign Creators assessment

HubSpot's Databricks for Data Studio connector is the starting point. With Data Hub Enterprise, it brings Databricks tables into Data Studio datasets that feed reports, workflows and CRM records, in the direction Databricks → HubSpot. Databricks also offers its own HubSpot ingestion connector, which covers marketing emails and, in Beta, contacts. The custom case is narrower: the full HubSpot model landing in Delta tables (all objects, engagements, associations, property history, marketing activity), portals without Data Hub Enterprise, computed tables written to specific objects and custom objects under agreed write rules and associations, near-real-time triggers, more than one workspace, and governance through Unity Catalog. CC builds it on the SQL Statement Execution API, the Jobs API and HubSpot's CRM APIs.

Scorecard
API accessOpen, OAuth M2M
Public docsExtensive
Compute costPlan per run
Build complexityModerate

Ratings are CC judgments from Databricks' public documentation and HubSpot's knowledge base. Warehouse sizing, workspaces and the tables in scope are confirmed with the client's data team during discovery.

Strength

SQL over HTTPS, governed by Unity Catalog

The SQL Statement Execution API runs parameterized SQL on a SQL warehouse and returns results inline (up to 25 MiB) or as external links (up to 100 GiB). The integration's service principal sees only what Unity Catalog grants it.

Plan for

Every read uses warehouse compute

A SQL warehouse bills while it runs, so frequent polling has a cost. CC reads only changed rows through Delta Change Data Feed, in batches, on a schedule agreed with the data team.

Gate

One writer per HubSpot field

If HubSpot's Data Studio connector already writes a field, the client decides whether it keeps that field or the custom build takes it over. The data team also approves which tables and columns may reach HubSpot.

02 — API modules

Which Databricks APIs does the integration use?

Seven parts of the Databricks platform matter to HubSpot. Two are existing connectors to scope around; five carry the custom build.

Starting point

HubSpot's Databricks for Data Studio

Built by HubSpot · Data Hub Enterprise

HubSpot's connector brings Databricks tables into Data Studio datasets. Datasets can drive reports and workflows, and can create or update CRM records against a match key.

  • Direction: Databricks → HubSpot
  • Up to 200 columns per warehouse source
  • Joins and calculated fields use HubSpot Credits; a direct sync to the CRM does not
Scope decision

Databricks' HubSpot ingestion connector

Lakeflow Connect · built by Databricks

Databricks offers a managed connector that ingests HubSpot data into Unity Catalog tables. Its documentation covers marketing emails, and contacts in Beta.

  • Direction: HubSpot → Databricks
  • Needs Unity Catalog and serverless compute
  • Decide early which objects it carries and which the custom build carries
Core

SQL Statement Execution API

/api/2.0/sql/statements

Runs SQL on a SQL warehouse over REST. The integration uses it to read changed rows and to merge HubSpot data into Delta tables.

  • Named parameters (:name) keep queries safe
  • INLINE up to 25 MiB; EXTERNAL_LINKS up to 100 GiB
  • wait_timeout of 0 or 5 to 50 seconds, then poll
Core

Delta Lake and Change Data Feed

table_changes · delta.enableChangeDataFeed

HubSpot data lands in Delta tables by MERGE, keyed on HubSpot IDs. Outbound reads use Change Data Feed, so only rows that changed since the last run go to HubSpot.

  • Rows marked insert, update or delete
  • Checkpoint on _commit_version
  • Re-running a load does not create duplicates
Core

Jobs API and triggers

Lakeflow Jobs · run-now and triggers

Jobs run on a schedule, when a source table updates, or when files arrive. A table-update trigger starts a push to HubSpot as soon as a score table changes.

  • Scheduled, table update, file arrival or continuous
  • run-now from the integration layer
  • One active run per job by default
Governance

Unity Catalog

Grants · row filters · column masks

Decides what the integration may read and write. The service principal gets USE CATALOG, USE SCHEMA and table privileges on named schemas only.

  • Column masks hide personal data before it leaves
  • Row filters limit which accounts sync
  • Lineage shows which tables feed HubSpot
Core

Service principals and OAuth M2M

/oidc/v1/token

The integration signs in as a Databricks service principal, not a person. It exchanges a client ID and secret for an access token.

  • Tokens valid for one hour, renewed automatically
  • Workspace-level or account-level tokens
  • One principal per workspace keeps access auditable
03 — Framework

How does the Databricks HubSpot integration work?

A CC-built integration layer sits between the lakehouse and HubSpot. Outbound, it pulls changed HubSpot records and merges them into Delta tables. Inbound, a Databricks job signals when a score or usage table changes, and the layer reads only the changed rows, applies the write rules and updates HubSpot in batches.

Databricks lakehouse
Delta tablesscores, usage, LTV, product events
Change Data Feedrows changed since the last run
Jobstable-update and scheduled triggers
Unity Cataloggrants, masks, lineage
CC integration layer
HubSpot extractorobjects, engagements, events → MERGE
Change readerSQL Statement API by commit version
Identity resolverHubSpot ID · email · domain · account key
Write ruleswhich object, which field, when
HubSpot writerbatch upserts, associations, replay
HubSpot
Contacts and companiesscores, usage, lifetime value
Deals and custom objectsproduct accounts, subscriptions
Associationslabelled links between records
Custom eventsproduct milestones on the timeline
Lists, workflows & reportssegments, alerts and views
Databricks → HubSpot (scores, usage and modeled records)HubSpot → Databricks (objects, engagements, associations and events into Delta)
Principle

HubSpot owns the customer record

Contacts, companies, deals and owners are created and edited in HubSpot. The lakehouse adds computed fields to those records and never creates a second copy of a person.

Principle

The lakehouse owns the math

Scores, lifetime value and usage rollups are computed in Databricks, where the data team can test and version them. HubSpot receives the result, not the raw events.

Principle

Governed at the source

The service principal sees only the schemas Unity Catalog grants it. Personal data columns are masked or left out of the views HubSpot reads.

04 — Process

What does Databricks HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. HubSpot data lands in the lakehouse first, so the data team can key every score on HubSpot IDs.

1

Discovery & access

List the workspaces, catalogs and tables in scope, the HubSpot subscription, and whether the Data Studio connector or the Databricks HubSpot connector is in use. Create a service principal per workspace with an OAuth secret.

Gate to next phaseAccess confirmed and table inventory signed
2

Ownership & write rules

For every HubSpot field the lakehouse feeds, agree the source column, the target object, when it may overwrite, and the match key. Agree which HubSpot data may land in Databricks.

Gate to next phaseSigned write-rule matrix and data approval
3

Landing design

Design the Delta tables for HubSpot objects, engagements, associations and events in a dedicated Unity Catalog schema, with grants, column masks and Change Data Feed on the outbound views.

Gate to next phaseSchema and grants approved by the data team
4

HubSpot data model

Create the custom properties, the Product Account custom object, association labels and custom event definitions in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build

Build the extractor (HubSpot → Delta by last-modified date), the change reader (Change Data Feed → HubSpot), the writer with an error replay queue, and the job triggers.

Gate to next phaseBoth directions running in sandbox with clean reconciliation
6

Backfill

Load HubSpot history into Delta, then send the first full set of scores and usage values to HubSpot, paced under HubSpot's API limits.

Gate to next phaseRow counts reconcile in both directions within an agreed tolerance
7

Workflows, parallel run & launch

Build score-driven lists, alerts and views with notifications paused, run two weeks in parallel, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the Databricks HubSpot integration sync?

Databricks table and column names below are examples; the client's data team names the real tables in discovery. HubSpot names are HubSpot's documented properties or the dbx_ custom properties in the schema below.

Databricks fieldHubSpot propertyObjectDirectionNotes
HubSpot → Delta tables
contacts tablehs_object_id + agreed propertiesContactHS → DBXMERGE on hs_object_id; lastmodifieddate drives incremental pulls.
companies tablehs_object_id + agreed propertiesCompanyHS → DBXSame pattern; domain kept for joins.
deals tabledealstage, amount, closedate, pipelineDealHS → DBXOwner and pipeline names resolved to labels.
line_items tablename, quantity, price, hs_product_idLine itemHS → DBXJoined to deals by association.
engagements tablescalls, emails, meetings, notes, tasksEngagement objectsHS → DBXOne table per type. Body text optional; governance decides.
associations tablefrom ID, to ID, association labelAll objects in scopeHS → DBXLets SQL join contacts, companies and deals.
property_history tableproperty, value, timestamp, sourceContact, Company, DealHS → DBXLifecycle and stage timing. Fields chosen in discovery.
marketing_activity tablemarketing email and form activityContactHS → DBXSource endpoints depend on HubSpot tier. Confirm in discovery.
Scores & metrics → HubSpot
account_scores.health_scoredbx_health_scoreCompanyDBX → HSOverwrites each run. Owned by Databricks.
lead_scores.propensity_scoredbx_propensity_scoreContactDBX → HSFeeds lists and lead routing.
ltv.predicted_ltvdbx_predicted_ltvCompanyDBX → HSCurrency.
product_usage.active_users_30ddbx_active_users_30dCompanyDBX → HSRolled up per account in the lakehouse.
product_usage.last_active_atdbx_last_active_atContactDBX → HSWritten only when newer than the HubSpot value.
product_usage.plan_tierdbx_plan_tierCompanyDBX → HSDropdown values agreed in discovery.
score_runs.model_versiondbx_model_versionCompanyDBX → HSShows which model produced the score.
Modeled records & associations
product_accounts tableProduct AccountCustom objectDBX → HSOne record per product account or workspace.
account_to_company mapProduct Account ↔ CompanyAssociationDBX → HSLabelled association.
user_to_account mapContact ↔ Product AccountAssociationDBX → HSRole on the account as the label.
subscriptions tableSubscription custom object or DealCustom objectDBX → HSChoice confirmed in discovery.
product_milestonesCustom event: Product milestoneContactDBX → HSTimeline entry, e.g. first project created.
Identity & keys
hubspot_id columnhs_object_idContact, Company↔ BothWritten back to the lakehouse after create, so later runs match on ID.
emailemailContact↔ BothFallback match key.
domaindomainCompany↔ BothFallback match key for companies.
account_keydbx_account_keyCompanyDBX → HSUnique property; the lakehouse's account ID.
06 — Auth & API

How are authentication and API limits handled?

Databricks limits below come from its API reference. Values Databricks does not publish as fixed numbers, such as warehouse cost, are confirmed with the client's data team.

TopicDatabricksHubSpot
Access modelA service principal per workspace, created by a workspace or account admin. Unity Catalog grants decide what it can read and write.Private app in the client portal, scoped per object. Custom objects and custom events need an Enterprise hub. The Data Studio warehouse connector needs Data Hub Enterprise; the custom build does not.
InterfacesSQL Statement Execution API (REST) on a SQL warehouse, Jobs API, Delta Lake tables with Change Data Feed, Unity Catalog.REST APIs: CRM objects, properties, associations, custom events, batch upserts.
AuthenticationOAuth M2M: client ID and secret exchanged at /oidc/v1/token for an access token valid one hour. Account-level tokens can reach several workspaces.Private app access token or OAuth 2.0 public app.
Query limitsResults INLINE up to 25 MiB or EXTERNAL_LINKS up to 100 GiB; statement text up to 16 MiB; external links expire within 15 minutes; results kept 12 hours.Per-10-second burst and daily limits by subscription tier; batch endpoints take up to 100 records per call.
FreshnessJobs run on a schedule, on table update, on file arrival or continuously. Change Data Feed returns changed rows by commit version.Writes are immediate. HubSpot changes are read by last-modified date.
Compute costEach read runs on a SQL warehouse, which bills while running. Not published as a fixed figure. Size and auto-stop confirmed with the data team.A direct warehouse-to-CRM sync in Data Studio uses no HubSpot Credits; joins and calculated fields there do.
Sensitive dataUnity Catalog grants, row filters and column masks applied to the service principal. Personal data excluded from outbound views unless approved.Sensitive data properties 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

Warehouse compute costHigh

Frequent polling keeps a SQL warehouse running. CC reads changed rows in batches, lines runs up with the warehouse's auto-stop, and writes the run frequency into the SOW.

More than one process writing the same fieldHigh

The Data Studio connector, the Databricks HubSpot connector and the custom build can overlap. A signed ownership matrix gives every HubSpot field one writer.

Large nightly pushes hit HubSpot limitsMedium

Scoring every record every night can mean hundreds of thousands of updates. The integration sends only values that changed, in batches of 100.

Identity across systemsMedium

Lakehouse account keys rarely match HubSpot IDs at the start. The HubSpot ID is written back to the lakehouse after the first match, and email and domain cover the rest.

Unity Catalog setup needs an adminMedium

Service principals, grants and column masks are set by the client's admins. Make them a client-owned dependency in the SOW, with a date.

Several workspacesLow

Development, production or regional workspaces each need their own principal and configuration. Only production writes to the live HubSpot portal.

Opportunities in HubSpot

Health and propensity scores where reps workHigh value

Account health and buying propensity sit on the company and contact record, so owners see risk and intent without opening a dashboard.

Product usage in workflowsHigh value

Active users, last activity and plan tier trigger onboarding, expansion and save plays in HubSpot workflows.

Full-funnel analysis in the lakehouseHigh value

HubSpot engagements, pipeline and marketing activity join billing and product data in Delta, so the data team can measure what actually drives revenue.

Product milestones on the timelineMedium value

Key product events appear on the contact timeline as custom events, next to emails, meetings and deals.

Model-driven segmentsMedium value

Lists built from dbx_ properties stay current as the models rerun, with no manual exports.

Lifetime value by source and campaignMedium value

Predicted lifetime value lands in HubSpot reports beside original source and campaign data.

Rollout order

Land HubSpot in the lakehouse, then send scores back.

Both directions share one identity map. Building the HubSpot → Delta copy first gives the data team HubSpot IDs to key every score on, so the return trip matches cleanly.

  1. Configure HubSpot's Data Studio connector for the tables it covers, where the portal has Data Hub Enterprise.
  2. Land HubSpot objects, engagements and associations in Delta, keyed on HubSpot IDs.
  3. Write the first computed table, usually account health or product usage, to company records.
  4. Add product accounts, associations and milestone events once the first scores are trusted.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the dbx_ prefix in a Databricks property group. Values are computed in the lakehouse; HubSpot stores the result.

Internal nameLabelObjectTypeSource / logic
dbx_account_keyLakehouse Account KeyCompanySingle-line textLakehouse account ID; unique
dbx_health_scoreHealth ScoreCompanyNumberAccount health model
dbx_propensity_scorePropensity ScoreContactNumberBuying propensity model
dbx_predicted_ltvPredicted LTVCompanyNumber (currency)Lifetime value model
dbx_active_users_30dActive Users (30 days)CompanyNumberDistinct active users, rolled up
dbx_last_active_atLast Product ActivityContactDate and time pickerLatest product event
dbx_plan_tierPlan TierCompanyDropdownCurrent product plan
dbx_usage_trendUsage TrendCompanyDropdownRising, flat or falling
dbx_model_versionScore Model VersionCompanySingle-line textModel that produced the scores
dbx_last_syncedLast Lakehouse SyncCompanyDate and time pickerSet on each successful write
dbx_product_account_idProduct Account IDProduct AccountSingle-line textProduct account key; unique
dbx_seatsSeatsProduct AccountNumberLicensed seats on the account
09 — Scope builder

Interactive scope builder

Choose the data and fields for this engagement and the direction each one 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
Databricks × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Databricks HubSpot integration FAQ

Does Databricks integrate with HubSpot?

Yes. With Data Hub Enterprise, HubSpot’s Databricks for Data Studio connector brings Databricks tables into Data Studio datasets that feed reports, workflows and CRM records, and Databricks offers its own HubSpot ingestion connector. Campaign Creators builds a custom layer on the SQL Statement Execution API, the Jobs API and HubSpot’s CRM APIs for what those do not cover, such as the full HubSpot model landing in Delta tables, portals without Data Hub Enterprise and near-real-time triggers.

What data syncs between Databricks and HubSpot?

HubSpot contacts, companies, deals, line items, engagements, associations, property history and marketing activity land in Delta tables. Health and propensity scores, predicted lifetime value, product usage, plan tier, product accounts and product milestones flow back to HubSpot records.

Which system owns which data?

HubSpot owns the customer record: contacts, companies, deals and owners are created and edited there. The lakehouse owns the math: scores, lifetime value and usage rollups are computed in Databricks and HubSpot receives the result. A signed ownership matrix gives every HubSpot field one writer.

What does setting up the Databricks HubSpot integration involve?

Seven phases, each closed by a client sign-off: discovery and access (a service principal per workspace), ownership and write rules, landing design in Unity Catalog, the HubSpot data model, the build, backfill, and workflows with a two-week parallel run before launch.

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

Timeline and cost depend on the workspaces, tables and directions in scope, the existing connectors in use and how often the sync runs. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.

Ready to Get More From HubSpot?

Whether you’re implementing HubSpot, optimizing what you already have, connecting systems, or scaling your customer experience, we’ll help you figure out the right next step.