Skip to main content
The HubSpot Load connector uses the Connect and Configure parameters to create a table of HubSpot data, which is then stored in your Snowflake cloud data warehouse. You do not need to use the Create Table component when using this connector, as the HubSpot Load component will create a new table or replace an existing table for you using the Destination parameters you define. If the component requires access to a cloud provider (AWS, Azure, or GCP), it will use the cloud credentials associated with your environment to access resources. To stage data to Azure Blob Storage, the Azure credentials associated with your environment must be assigned the Storage Blob Data Contributor role. For more information, read User assigned with the Storage Blob Data Contributor role.
For Snowflake projects, this component supersedes the HubSpot Query component, which is no longer available for new pipelines.Existing pipelines with the HubSpot Query component will continue to work as expected.Databricks and Amazon Redshift projects should continue to use the HubSpot Query component.

​
Properties

Reference material is provided below for the Connect, Configure, Destination, and Advanced Settings properties.
​
Name
string
required
A human-readable name for the component.

​
Connect

​
Authentication Method
drop-down
required
Choose OAuth 2.0 Authorization Code or API key as the authentication method.
​
Authentication
drop-down
required
Choose your OAuth connection from the drop-down menu.Click Manage to navigate to the OAuth connections list to review OAuth connections and to add new connections. Read OAuth to learn how to create an OAuth connection.
​
Private App Token
drop-down
required
This parameter is only available when you choose API Key as the authentication method.Choose the secret definition that represents your credentials for this connector.If you have not already saved your credentials for this connector as a secret definition, click Add secret to create a secret definition representing these credentials. Read Secrets and secret definitions for details about creating a secret definition.Read HubSpot authentication guide to learn how to obtain a Private App token.
​
Connection Options
column editor
  • Parameter: A JDBC parameter supported by the database driver. The available parameters are explained in data model. Manual setup is not usually required, since sensible defaults are assumed.
  • Value: A value for the given parameter.
Click the Text Mode toggle at the bottom of the Connection Options dialog to open a multi-line editor that lets you add items in a single block. For more information, read Text mode.To use grid variables, select the Use Grid Variable checkbox at the bottom of the Connection Options dialog.

​
Configure

​
Load Type
drop-down
required
  • Full Load: Load all data from the data source on every pipeline run.
  • Incremental Load: Load only new or updated data since the last successful pipeline run using a high-water mark column.
​
Mode
drop-down
required
  • Basic: Configure data selection using the Data Source, Data Selection, Data Source Filter, Combine Filters, and Row Limit properties.
  • Advanced: Write your own SQL query using the SQL Query property.
  • Incremental: Use incremental data loading with a high-water mark column. Available when Load Type is set to Incremental Load.
​
SQL Query
code editor
Write an SQL query to retrieve your data. Only available for Snowflake destinations when Mode is set to Advanced.
​
Schema
drop-down
required
Select the schema to use when browsing available data sources. Only available for Snowflake destinations.
​
Data Source
drop-down
required
Select the data source to query from. Available when Mode is set to Basic.
​
Data Selection
dual listbox
required
Select the columns to include from the data source. Available when Mode is set to Basic.
​
Data Source Filter
grid
Filter the rows returned from the data source. Available when Mode is set to Basic.
​
Combine Filters
drop-down
required
Choose how to combine multiple filters. Select AND to return rows matching all filters, or OR to return rows matching any filter. Available when Mode is set to Basic.
​
Row Limit
integer
The maximum number of rows to return from the data source. Leave blank to return all rows. Available when Mode is set to Basic.
​
High Water Mark Selection
drop-down
required
Select the column to use as the high-water mark for incremental loading. Available when Load Type is set to Incremental Load.

​
Destination

Select your cloud data warehouse.
​
Destination
drop-down
required
Select the destination for your data. This is either in Snowflake as a table or as files in cloud storage.
  • Snowflake: Load your data into a table in Snowflake. The data must first be staged via Snowflake or a cloud storage solution.
  • Cloud Storage: Load your data directly into files in your preferred cloud storage location. The format of these files can differ between source systems and will not have a file extension so we suggest inspecting the output to determine the format of the data.
​
Warehouse
drop-down
required
The Snowflake warehouse used to run the queries. The special value [Environment Default] uses the warehouse defined in the environment. Read Overview of Warehouses to learn more.
​
Database
drop-down
required
The Snowflake database to access. The special value [Environment Default] uses the database defined in the environment. Read Databases, Tables and Views - Overview to learn more.
​
Schema
drop-down
required
The Snowflake schema. The special value [Environment Default] uses the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.
​
Table Name
string
required
The name of the table to be created in your Snowflake database. You can use a Table Input component in a transformation pipeline to access and transform this data after it has been loaded.
​
Load Strategy
drop-down
required
Define what happens if the table name already exists in the specified Snowflake database and schema.
  • Replace: If the specified table name already exists, that table will be destroyed and replaced by the table created during this pipeline run.
  • Truncate and Insert: If the specified table name already exists, all rows within the table will be removed and new rows will be inserted per the next run of this pipeline.
  • Fail if Exists: If the specified table name already exists, this pipeline will fail to run.
  • Append: If the specified table name already exists, then the data is inserted without altering or deleting the existing data in the table. It’s appended onto the end of the existing data in the table. If the specified table name doesn’t exist, then the table will be created, and your data will be inserted into the table.
​
Primary Keys
dual listbox
Select one or more columns to be designated as the table’s primary key.
​
Clean Staged files
boolean
required
  • Yes: Staged files will be destroyed after data is loaded. This is the default setting.
  • No: Staged files are retained in the staging area after data is loaded.
​
Stage Access Strategy
drop-down
Select the stage access strategy. The strategies available depend on the cloud platform you select in Stage Platform.
  • Credentials: Connects to the external stage (AWS, Azure) using your configured cloud provider credentials. Not available for Google Cloud Storage.
  • Storage Integration: Use a Snowflake storage integration to grant access to Snowflake to read data from and write to a cloud storage location. This will reveal the Storage Integration property, through which you can select any of your existing Snowflake storage integrations.
​
Stage Platform
drop-down
required
Use the drop-down menu to choose where the data is staged before being loaded into your Snowflake table.
  • Amazon S3: Stage your data on an AWS S3 bucket.
  • Snowflake: Stage your data on a Snowflake internal stage.
  • Azure Storage: Stage your data in an Azure Blob Storage container.
  • Google Cloud Storage: Stage your data in a Google Cloud Storage bucket.

​
Advanced Settings

​
Auto Debug
drop-down
required
Choose whether to automatically log debug information about your load. These logs can be found in the task history and should be included in support requests concerning the component. Turning this on will override any debugging connection options.
​
Debug Level
drop-down
required
The level of verbosity with which your debug information is logged. Levels above 1 can log huge amounts of data and result in slower execution. These logs can be found in the Message field of the task details after pipeline execution and should be included in support requests concerning the component.
  1. Will log the query, the number of rows returned by it, the start of execution and the time taken, and any errors.
  2. Will log everything included in Level 1, plus cache queries and additional information about the request, if applicable.
  3. Will additionally log the body of the request and the response.
  4. Will additionally log transport-level communication with the data source. This includes SSL negotiation.
  5. Will additionally log communication with the data source, as well as additional details that may be helpful in troubleshooting problems. This includes interface commands.
​
Parse 'Null' & Empty Strings as NULL
boolean
required
Converts common strings that represent null into a null value. This is case-sensitive and works with the following strings: "", “NULL”, “NUL”, “Null”, “null”. The default is No.
Currently, this property is only applicable when using Snowflake as your destination.
​
Trim String Columns
boolean
required
When Yes, remove leading and trailing characters from a string column. The default is No.

​
Data model

The JDBC driver for this component models HubSpot APIs as relational tables, views, and stored procedures, which are documented in the data model. You’ll also find API limitations and requirements. The connection option SupportEnhancedSQL is set to true by default and typically circumvents most API limitations. This connector also allows you to query system tables in Advanced mode. To see the available system tables in the data model, read the System Tables section of the data model. For more information about using system tables, read our System tables guide.