My team and I have recently rolled out the Snowflake → HubSpot integration (Marketplace link) and curious to see if any others have experienced the below & able to assist
Our Snowflake setup is below:
Master Table (handles 90% of all required property mapping)
Mananged via DBT daily incremental update
2-3 additional tables (used for supplemental data)
Managed via DBT daily full refresh
Situation 1:
As we rely on the above tables for property mapping via the integration, we’ve observed that when DBT executes a full refresh for the additional tables, the integration detects the rapid drop and refresh of the tables it triggers the update in HubSpot changing property values to Null then recommencing a full refresh when the table is rebuilt (happens within a 30 second window) with the prior properties.
- Is there a way to combat this? can we set polling to x per hour or at x time on x hour?
When setting up a sync (or when having multiple) is it possible to change the name of the sync from the default “object name” to something that is more descriptive?
Hey @AdamDx - thanks so much for posting in the Community!
I’d like to tag in some Community experts to see if they have any insight on best practices regarding this setup! @HubSpot_Corey, @ScottPennwood, and @ChristinaKay - any thoughts on this?
Shane, Senior Community Moderator
Hi @AdamDx great breakdown, this behavior is pretty common when the Snowflake > HubSpot sync runs more often than your DBT refresh window. During a full refresh, Snowflake momentarily drops and recreates the tables, so HubSpot sees them as “emptied” and pushes nulls before your data rebuilds.
HubSpot now offers Snowflake Direct Sync, which lets you connect a Snowflake table or view directly to HubSpot CRM objects and configure recurring scheduled syncs. Syncs are scheduled rather than real-time, and each run evaluates the source data and updates records where changes are detected: Connect HubSpot and Snowflake Data Sync (legacy)
Another option is to use views or staging tables that don’t get dropped, DBT can write to temp tables and swap them atomically to prevent the null state.
For naming, the sync label currently inherits the object name, but you can rename the connection in Snowflake’s “Integration Details” tab, which then reflects in HubSpot’s sync list after refresh.
Moderator Note: this post was reviewed for relevancy and optimized for clarity on September 29, 2026. Thank you for your contributions to the HubSpot Community!
