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 <> Snowflake Integration

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

Snowflake × HubSpot

How a company that models its customer data in Snowflake (health scores, product usage, revenue and lifetime value) can put those numbers on the HubSpot records that reps, marketers and workflows act on, and keep HubSpot data in Snowflake for analysis. HubSpot's own Snowflake tools are the starting point; a custom build on Snowflake's APIs covers the rest.

SQL API (REST)Streams & triggered tasksSnowparkExternal access integrationsKey-pair JWT or OAuthHubSpot data sync & data share
Platform ownerSnowflake Inc.
Integration typeHubSpot data sync and data share, plus custom build
Primary directionSnowflake → HubSpot (modeled data)
FeasibilityStrong fit
API accessOpen API
01 — Summary

Does Snowflake integrate with HubSpot?

Snowflake is where many companies calculate the numbers sales and marketing need: product usage, account health, lifetime value, churn risk. Those numbers only change outcomes when they reach the HubSpot record a rep opens or a workflow reads, and when HubSpot activity flows back into Snowflake for analysis.

API access
Open APIOpen with conditionsGated API

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

Open API. The SQL API is documented publicly. The client's Snowflake admin creates the service user and role.

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

Snowflake exposes its data through a documented REST SQL API and built-in change tracking, so modeled warehouse data can drive HubSpot records, lists and workflows.

Campaign Creators assessment

HubSpot's own tools are the starting point. With Data Hub Enterprise, HubSpot's Snowflake data sync reads a table or view on a schedule and creates or updates contacts, companies, deals and custom objects, and the Snowflake Data Share makes HubSpot objects, associations, events and property history queryable in Snowflake. The custom case is narrower. It covers what those tools don't: portals without Data Hub Enterprise, per-field write rules (fill blanks only, never overwrite a rep's edit, write only on change), custom events on the HubSpot timeline, near-real-time pushes driven by Snowflake streams, labeled associations, more than one Snowflake account or database feeding one portal, and governance over which columns and rows leave the warehouse. Compute is a planning item: every query runs on a Snowflake warehouse that bills credits while it runs.

Scorecard
API accessOpen, self-serve
Public docsExtensive
Compute costPlan for it
Build complexityModerate

Ratings are CC judgments from Snowflake's public documentation and HubSpot's knowledge base. Warehouse size, schedule and credit budget are set with the client's Snowflake admin during discovery.

Strength

Change tracking is built in

Snowflake streams record inserts, updates and deletes on a table, and triggered tasks run only when a stream has new data (every 30 seconds by default, down to 10). Only changed rows go to HubSpot.

Plan for

Who owns each field

A warehouse value written every hour will overwrite a rep's manual edit unless rules say otherwise. Each synced property gets one owner and one write rule, written into the SOW.

Gate

Tier and security decisions first

Decide which flows HubSpot's data sync covers under Data Hub Enterprise and which need the custom build, and have the client's Snowflake admin approve the service user, role, warehouse and network policy.

02 — API modules

Which Snowflake APIs does the integration use?

Seven parts of Snowflake and HubSpot matter here. HubSpot's two Snowflake tools cover standard flows; the custom build uses Snowflake's APIs and in-database features for the rest.

Starting point

HubSpot's Snowflake data sync

Built by HubSpot · Data Hub Enterprise

Syncs a Snowflake table or view one way into HubSpot on a schedule you choose. Rules can be create and update, create only, or update only.

  • Contacts, companies, deals and custom objects
  • Up to 10 GB and 200 columns per table or view
  • Up to 30 million records per sync run
Starting point

HubSpot's Snowflake Data Share

Built by HubSpot · Data Hub Enterprise

Makes HubSpot data queryable with SQL inside the client's Snowflake account, so models can join CRM data with product and finance data.

  • Objects, associations, events, property history
  • Lists, owners, pipelines and stages
  • Live schema up to every 15 minutes; daily schema
Core

SQL API

REST · submit, check status, cancel

Snowflake's REST API for running SQL. The integration layer uses it to read approved views and to record HubSpot IDs and sync status back in Snowflake.

  • Queries plus most DDL and DML statements
  • Multiple statements, stored procedures, transactions
  • OAuth, key-pair JWT or workload identity federation
Core

Streams & triggered tasks

Change data capture inside Snowflake

A stream tracks row changes on a model table. A triggered task runs when the stream has data and writes only the changes to an outbound queue table.

  • No compute used until data changes
  • One task run at a time; runs again if new data arrived
  • Serverless or on a named warehouse
Core

Snowpark & stored procedures

Python, Java or Scala in Snowflake

Scores, rollups and payload shaping run where the data lives, so the integration layer receives HubSpot-ready rows instead of raw tables.

  • Health, fit and propensity scores computed in place
  • Rollups at contact, company and custom object level
  • One definition of each metric for every report
Option

External access integrations

Network rule + secret + integration

Lets a Python procedure in Snowflake call the HubSpot API directly over an allowed network rule, with the token held in a Snowflake secret. Useful when the client wants no middle tier.

  • Egress only to hosts the network rule allows
  • Credentials stored as Snowflake secrets
  • Retries and replay must be built into the procedure
Scope decision

Roles, warehouses & credits

Least privilege and compute budget

Every query runs on a warehouse that bills per second, with a 60-second minimum each time it starts. Schedule, warehouse size and auto-suspend are agreed before build.

  • Dedicated read-only role on approved views
  • Dedicated small warehouse with auto-suspend
  • Change-only reads keep credits predictable
03 — Framework

How does the Snowflake HubSpot integration work?

Models stay in Snowflake. A CC-built integration layer reads only approved views and changed rows, applies governance and write rules, matches each row to the right HubSpot record, and writes in batches. HubSpot data returns to Snowflake through HubSpot's Data Share.

Snowflake account
Modeled tables & viewsscores, usage, revenue, LTV
Streamsrows changed since last read
Triggered taskswrite changes to an outbound queue
HubSpot Data ShareCRM data for joins and checks
CC integration layer
Secure readerSQL API · key-pair JWT · read-only role
Governance filterapproved columns and row filters
Identity resolverHubSpot ID · email · domain · external ID
Write rulesfield owner, fill blanks, change only
HubSpot writerbatch upserts, associations, events, replay
HubSpot
Contactsusage, scores, lifecycle signals
Companiesaccount metrics and health
Dealsexpansion and renewal signals
Custom objectssubscriptions, workspaces, licenses
Custom events & workflowstimeline entries that trigger automation
Snowflake → HubSpot (primary flow)HubSpot → Snowflake (Data Share, plus HubSpot IDs and sync status written back)
Principle

Compute in Snowflake, act in HubSpot

Scores and rollups are calculated once in the warehouse. HubSpot stores the result on the record where people and workflows use it.

Principle

Send changes, not tables

Streams and change-only reads keep HubSpot API calls and Snowflake credits low, and make every sync run small enough to replay.

Principle

Govern at the source

The integration reads only views the client approves. Restricted columns and rows never leave Snowflake.

04 — Process

What does Snowflake HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. The first data set goes live while the next is being built.

1

Use-case inventory

List the decisions sales, marketing and service should make from warehouse data, and the Snowflake tables or models that hold each number.

Gate to next phaseSigned list of data sets in priority order
2

Native-or-custom decision

For each data set, decide whether HubSpot's Snowflake data sync covers it under Data Hub Enterprise, or whether it needs write rules, events, associations or timing that call for the custom build.

Gate to next phaseSigned split of flows between native and custom
3

Access & governance

The client's Snowflake admin creates a service user with key-pair authentication, a read-only role, a dedicated warehouse and the approved views. Compliance signs off the column list.

Gate to next phaseTest query returns approved columns only
4

HubSpot data model

Create the properties, custom objects, association labels and custom event definitions in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build

Build streams, triggered tasks and the integration layer for the first data set, with identity matching, write rules, idempotent upserts and a replay queue.

Gate to next phaseFirst data set syncing in sandbox and reconciling
6

Backfill

Load current values for all matched records once, in batches sized to HubSpot's API limits and the agreed warehouse budget.

Gate to next phaseHubSpot values match Snowflake within an agreed tolerance
7

Workflows, parallel run & launch

Build lists and workflows with sends paused, run in parallel for two weeks, review credit use, then switch on.

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

What does the Snowflake HubSpot integration sync?

Warehouse column names are defined by each client's models, so the source column describes the data plainly. Exact table, view and column names are confirmed during discovery.

Snowflake fieldHubSpot propertyObjectDirectionNotes
Identity & keys
HubSpot record ID (stored in Snowflake)hs_object_idContact / Company↔ BothBest match key once known. Written back to Snowflake after first match.
Email addressemailContactSNOW → HSMatch key for contacts without a stored HubSpot ID.
Company domaindomainCompanySNOW → HSMatch key for companies without a stored HubSpot ID.
Customer account IDsnow_account_idCompanySNOW → HSClient's own account key. Unique property; used for batch upserts.
User IDsnow_user_idContactSNOW → HSProduct user key. Unique property.
Sync status and last syncedStatus table in Snowflake—HS → SNOWWritten back by the integration layer for audit.
Account metrics · companies
Annual recurring revenuesnow_arrCompanySNOW → HSFrom the revenue model. Snowflake owns this field.
Plan or tiersnow_plan_tierCompanySNOW → HSDropdown values agreed in discovery.
Lifetime valuesnow_ltvCompanySNOW → HSModel output. Snowflake owns this field.
Health scoresnow_health_scoreCompanySNOW → HSModel output, 0 to 100.
Churn risk bandsnow_churn_riskCompanySNOW → HSLow, medium, high. Can trigger a CSM workflow.
Seats purchased vs usedsnow_seats_usedCompanySNOW → HSRollup from product data.
Product usage · contacts
Last active datesnow_last_activeContactSNOW → HSWrite only when changed.
Active days, last 30snow_active_days_30ContactSNOW → HSRollup from product events.
Key feature adoptedsnow_features_adoptedContactSNOW → HSMultiple checkboxes.
Product-qualified flagsnow_pqlContactSNOW → HSCan move lifecycle stage by workflow, not by direct write.
Milestone reachedCustom event: Product milestoneContactSNOW → HSTimeline entry that workflows can trigger on.
Phone, job titlephone, jobtitleContactSNOW → HSFill blanks only. HubSpot edits win.
Custom objects & associations
Subscription or licenseSubscription (custom object)Custom objectSNOW → HSPlan, term, renewal date. Object design confirmed in discovery.
Workspace or product accountWorkspace (custom object)Custom objectSNOW → HSFor multi-workspace customers.
Account-to-user linkAssociation (labeled)Company ↔ ContactSNOW → HSLabels such as Admin or Billing contact.
Subscription-to-company linkAssociationCustom object ↔ CompanySNOW → HSSet from the customer account ID.
Renewal opportunityDeal in renewal pipelineDealSNOW → HSCreated when renewal date enters the agreed window.
HubSpot → Snowflake
Contacts, companies, dealsHubSpot Data Share viewsAll objectsHS → SNOWQueried in Snowflake for attribution and models.
Email and web eventsHubSpot Data Share eventsEventsHS → SNOWJoins marketing activity to product usage.
Property historyHubSpot Data Share historyAll objectsHS → SNOWMost recent 45 values per contact, 20 for other objects.
06 — Auth & API

How are authentication and API limits handled?

Snowflake access is self-serve for the client's admin. Values Snowflake does not publish are marked for confirmation.

TopicSnowflakeHubSpot
Access modelA service user and dedicated role created by the client's Snowflake admin, with access to approved views only.Private app token for the custom build. Data Hub Enterprise for HubSpot's data sync and Data Share.
InterfacesSQL API (REST) to submit statements, check status and cancel; Snowpark and stored procedures in the warehouse; external access integrations for outbound calls.REST APIs: CRM objects, batch upserts, associations, custom events, imports.
AuthenticationKey-pair JWT (valid at most one hour), OAuth, or workload identity federation.Private app access token or OAuth 2.0, scoped per object.
PermissionsUsage on one warehouse, database and schema; select on approved views. Nothing broader.Scopes for the objects, associations and events in scope.
FreshnessTriggered tasks run when a stream has data (30 seconds by default, 10 at minimum). Data Share live schema refreshes up to every 15 minutes.Writes are immediate; batch endpoints handle volume.
Cost & limitsCompute billed per second while a warehouse runs, 60-second minimum per start. SQL API rate limits: not published. Confirm with Snowflake.Per-10-second burst and daily limits by subscription tier.
Network & sensitive dataNetwork policies may restrict inbound access; allowlist the integration layer's addresses and HubSpot's ranges if the data sync is used.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

Compute cost on every runHigh

Each read resumes a warehouse and bills at least a minute. Change-only reads, a small dedicated warehouse, auto-suspend and an agreed schedule keep the credit budget predictable.

Warehouse values overwriting HubSpot editsHigh

If both systems write the same property, the last write wins. Every synced field gets an owner and a rule (overwrite, fill blanks, or never) before the build starts.

Native or custom, field by fieldMedium

HubSpot's data sync needs Data Hub Enterprise and runs on a schedule. Agreeing which flows it handles avoids building twice and keeps the custom scope narrow.

HubSpot API limits on large tablesMedium

A full table pushed every hour can exhaust daily limits. The integration sends changed rows only and uses batch endpoints.

Personal data leaving the warehouseMedium

Only approved columns and rows leave Snowflake. The views enforce this, and compliance signs off the column list.

Stream stalenessLow

A stream that is not read before its retention window ends becomes stale. Triggered tasks and monitoring keep streams current.

Opportunities in HubSpot

Scores reps can act onHigh value

Health, fit and churn risk sit on the company record, so reps and CSMs see them in views, sequences and tasks.

Product-qualified leads into workflowsHigh value

A usage milestone becomes a HubSpot custom event that enrolls the contact in the right workflow within minutes.

Renewals and expansion in the pipelineHigh value

Subscriptions as custom objects create renewal deals on time, with seat and usage data attached.

Closed-loop analysisMedium value

HubSpot's Data Share puts marketing and sales activity next to revenue in Snowflake, so attribution models use real outcomes.

One definition of each metricMedium value

Revenue and health are calculated once in Snowflake, so HubSpot reports and warehouse dashboards agree.

No more spreadsheet importsMedium value

Scheduled CSV imports of warehouse exports are replaced by an audited, replayable sync.

Decision guide

Use HubSpot's tools where they fit. Build where they don't.

HubSpot's Snowflake data sync and Data Share handle standard, scheduled flows under Data Hub Enterprise. The custom build is scoped only to what those tools don't cover, so the client pays for the gap, not for a rebuild.

  1. HubSpot data into Snowflake for analysis: HubSpot's Data Share.
  2. Scheduled table-to-object syncs with simple create or update rules: HubSpot's data sync.
  3. Per-field write rules, custom events, labeled associations or near-real-time triggers: custom build.
  4. Portals without Data Hub Enterprise, or several Snowflake accounts into one portal: custom build.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the snow_ prefix in a Snowflake property group. Values are calculated in Snowflake so every report agrees.

Internal nameLabelObjectTypeSource / logic
snow_account_idSnowflake Account IDCompanySingle-line textClient's customer account key; unique
snow_user_idProduct User IDContactSingle-line textProduct user key; unique
snow_arrARRCompanyNumber (currency)Revenue model output
snow_plan_tierPlan TierCompanyDropdownCurrent plan from billing model
snow_ltvLifetime ValueCompanyNumber (currency)LTV model output
snow_health_scoreHealth ScoreCompanyNumberModel output, 0 to 100
snow_churn_riskChurn RiskCompanyDropdownLow, medium, high
snow_seats_usedSeats UsedCompanyNumberActive seats from product data
snow_last_activeLast Active DateContactDate pickerLatest product activity
snow_active_days_30Active Days (30)ContactNumberDistinct active days, last 30
snow_features_adoptedFeatures AdoptedContactMultiple checkboxesKey features used at least once
snow_pqlProduct QualifiedContactSingle checkboxPQL rule in Snowflake model
09 — Scope builder

Interactive scope builder

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

Scope summary

0Fields
0Inbound
0Write-back
10 — Sources

Sources & verification

Based on public documentation from Snowflake and HubSpot. Credit budget, network policy and table names are confirmed with the client's Snowflake admin during discovery.

Snowflake × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Snowflake HubSpot integration FAQ

Does Snowflake integrate with HubSpot?

Yes. With Data Hub Enterprise, HubSpot's Snowflake data sync reads a table or view into HubSpot on a schedule, and the Snowflake Data Share makes HubSpot data queryable in Snowflake. Campaign Creators adds a custom build on Snowflake's SQL API for what those tools don't cover, such as per-field write rules, custom events, near-real-time pushes and column-level governance.

What data syncs between Snowflake and HubSpot?

Modeled Snowflake data such as product usage, health scores, revenue and lifetime value is written to HubSpot contacts, companies, deals and custom objects, and can create custom events that trigger workflows. HubSpot objects, associations, events and property history flow back to Snowflake through the Data Share, along with HubSpot IDs and sync status.

Which system owns which data?

Scores and rollups are calculated once in Snowflake, and HubSpot stores the result where people and workflows use it. Each synced property gets one owner and one write rule in the SOW, so a warehouse value never overwrites a rep's edit unless agreed. Restricted columns and rows never leave Snowflake.

What does setting up the Snowflake HubSpot integration involve?

Seven phases, each closed by a client sign-off: a use-case inventory, the native-or-custom decision for each data set, access and governance (a service user with key-pair authentication, a read-only role and a dedicated warehouse), the HubSpot data model, the build, a backfill, and a two-week parallel run before workflows are switched on.

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

Timeline and cost depend on the data sets in scope, how many need the custom build rather than HubSpot's native sync, and the agreed Snowflake compute budget. 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.