About Openflow Connector for HubSpot¶

Note

The connector is subject to the Connector Terms.

This topic describes the basic concepts of Openflow Connector for HubSpot, its workflow, and limitations.

The Openflow Connector for HubSpot ingests HubSpot data into Snowflake. It uses the HubSpot API to retrieve data, which is then stored in a Snowflake table. Data ingestion happens in the following two phases:

  1. Initial load, where all data is retrieved during the first API call.

  2. Incremental load, which merges the updates and new data into the destination table and uses timestamps from previous calls to limit the result to the issues that were updated since the last data load.

For more information about HubSpot private apps, see Private apps.

Workflow¶

  1. A HubSpot administrator performs the following tasks:

    1. Generates an API token within the HubSpot instance with the necessary scopes required for the API requests intended to make. This token is used by the connector for authentication.

    2. Defines the criteria to search objects, for example, the object type and updated after fields.

  2. A Snowflake account administrator performs the following tasks:

    1. Downloads and imports the connector definition file into the Snowflake Openflow canvas.

    2. Configures the connector parameters:

      • Provides the HubSpot private app API token.

      • Defines the criteria for the objects being ingested by providing filters.

      • Sets the desired database and schema names within Snowflake.

    3. Runs the connector flow. Upon execution, the connector does the following:

      1. Creates an API call to fetch objects from the configured HubSpot instance.

      2. Extracts the relevant data.

      3. Creates the configured destination table in the Snowflake database if the API call returned at least one result.

      4. Loads the processed data into the specified Snowflake table.

Limitations¶

  • One connector instance can be associated with only one HubSpot object.

  • Currently, the connector supports basic authentication using a HubSpot private app and API token. This means that the connector is only able to ingest data that is accessible to the owner of the API token.

  • The processors are designed to work on the primary node only with one thread.

  • The number of calls your private app can make is based on your account subscription. To learn more about HubSpot private app limits, see Private app limits.

Next steps¶

Set up the Openflow Connector for HubSpot

Language: English