HUBSPOT → SNOWFLAKE
Replicate supported HubSpot CRM, marketing, engagement, and commerce data into Snowflake on a schedule.
Supaflow reads the HubSpot objects and properties available to the connection, then loads selected data into Snowflake for attribution, lifecycle, service, and revenue reporting. Use OAuth or a Private App access token, with incremental reads for supported CRM, marketing email, and engagement objects and full refresh for Behavioral Events and lookup-style data. Every connector is included on every Supaflow plan — you pay only for the compute your pipelines consume.
For RevOps, marketing analytics, and data teams joining HubSpot records with finance, product, and support data — with no per-row fees.
Verified connector behavior and known limits for this source.
| Feature | How it works | Limit / caveat |
|---|---|---|
| Authentication | Use HubSpot OAuth for user-delegated access with automatic token refresh, or a Private App access token managed by your team. | The selected account or token must have read access to every object and property the pipeline should sync. |
| Supported object catalog | Select configured CRM, engagement, marketing, commerce, list, owner, team, user, role, and pipeline objects that are available to the connection. | Custom properties on supported objects are included. Portal-specific custom objects and forms are not currently selectable. |
| Incremental and full-refresh reads | Supaflow keeps progress separately for supported incremental objects. Behavioral Events, lists, memberships, and other lookup-style objects use full refresh. | — |
| Properties and related data | Supported object properties are discovered from HubSpot. Configured association mappings and property-history features can produce related tables for the objects that enable them. | Coverage follows the connector catalog and the permissions granted to the connection; it is not automatic coverage of every association or history type in a HubSpot portal. |
| Archived records | For eligible objects, the connector can request archived records that HubSpot still exposes and include them in the source read. | A permanently removed record is no longer available through an ordinary object read, so the connector does not provide hard-delete events. |
| Rate limiting and retry | Supaflow retries HubSpot throttling with backoff and honors HubSpot retry timing when it is provided. | Large object selections and other integrations using the same account can extend a scheduled run. |
| Snowflake loading | Selected HubSpot objects load into Snowflake tables with destination-friendly types and saved source progress for incremental objects. | — |
Every Supaflow connector is included on every plan at no extra cost. You pay only for compute consumed, measured in Supaflow Credits (1 credit = 1 billable job hour on an S (Small) Agent node). No per-row fees.
Choose the supported objects and fields required for your warehouse model, pair them with your Snowflake destination, and set the schedule in Supaflow. The same source can also be paired with other supported destinations.
Supported CRM, marketing email, and engagement objects can resume from a saved position, while Behavioral Events, lookup data, and membership data refresh in full. That distinction lets each object use the read behavior it supports.
These source-specific cases affect discovery, parsing, or incremental reads. The notes below explain the failure mode and connector behavior.
Failure mode: An object can be supported by the connector but absent from schema selection when the OAuth grant, Private App scopes, HubSpot subscription, or connected user does not expose it.
Evidence: When an object is unavailable, it is either absent from schema selection or its Job Details entry reports the HubSpot permission failure.
Fix: Confirm the object is supported, grant the required read access, reconnect OAuth when scopes change, and refresh the source schema.
Failure mode: Behavioral Events, lists, memberships, and lookup-style data are read again in full rather than resuming from a saved position.
Evidence: Full-refresh objects read their current rows again on every scheduled run; supported incremental objects resume from saved progress.
Fix: Expect full refresh for Behavioral Events, lists, memberships, and lookup objects; use saved-progress behavior only where the source docs mark an object Incremental.
Failure mode: Treating every relationship or property change in a HubSpot portal as automatically available creates missing-table expectations.
Evidence: Related association or history tables appear in schema selection only for supported objects that expose them; other portal relationships do not create selectable tables.
Fix: Review the discovered schema for the related tables your selected objects expose, and do not assume portal-specific association types are included.
Failure mode: HubSpot can still return an archived record for some objects, while a permanently removed record has no row for the connector to read.
Evidence: For eligible objects, destination rows can include the archived state while HubSpot still returns the record; permanently removed records produce no deletion row.
Fix: Use the archived state when it is available. If permanent deletion reconciliation is required, design a separate source-of-truth process for that policy.
Choose OAuth or Private App authentication and grant read access to the supported objects and properties the pipeline needs.
HubSpot source docs→Review the catalog available to the connection, then select the CRM, marketing, engagement, commerce, and lookup data required by your model.
Choose the Snowflake destination and target database and schema for the selected HubSpot tables.
Snowflake destination docs→Run the pipeline on a cron or interval schedule. Incremental objects resume from saved progress; Behavioral Events and other full-refresh objects are read again.
Schedules docs→HubSpot documents Snowflake Data Share for eligible Data Hub Enterprise accounts, and a separate Direct Sync feature that moves Snowflake data into HubSpot. Supaflow is a scheduled pipeline for reading supported HubSpot data and loading it into Snowflake or another supported destination.
Yes. Choose Private App authentication and enter a token with read scopes for the objects you plan to sync. OAuth is also supported and is the default authentication method.
Not currently. Custom properties on supported objects are discovered when the connection can read them, but portal-specific custom objects and forms are not selectable.
The connector can create association and property-history tables for mappings and object features enabled in its catalog. Review the discovered schema for your selected objects; the connector does not claim automatic coverage of every portal-specific relationship or history type.
It can request archived records for eligible objects while HubSpot still exposes them. It does not receive a hard-delete event after a record is permanently removed.
HubSpot pipelines are not priced by rows or connector count. Every Supaflow connector is included on every plan at no extra cost. You pay only for compute consumed, measured in Supaflow Credits (1 credit = 1 billable job hour on an S (Small) Agent node). No per-row fees. See the pricing page for current credit packages and the free tier.
The HubSpot source and Snowflake destination, plus other Supaflow connectors you can pair into a Snowflake pipeline.
Source connector overview and capabilities.
Destination connector overview and capabilities.
For standard and custom Salesforce objects in the same warehouse.
Pair CRM records with operational data managed in Airtable.
Pair HubSpot data with planning and enrichment data in Google Sheets.
Browse the full catalog of sources and destinations.
Authentication, supported objects, sync behavior, schema refresh, and troubleshooting.
Connect the warehouse and review destination configuration and loading behavior.
Official HubSpot documentation for its Data Hub Enterprise Snowflake sharing option.
Official HubSpot documentation for the reverse-direction Snowflake-to-HubSpot sync option.
Every connector is included on every Supaflow plan — you pay only for the compute your pipelines consume. OAuth or Private App authentication with object-specific sync behavior.