Edit

Share via


Copy data from HubSpot using Azure Data Factory or Synapse Analytics

APPLIES TO: Azure Data Factory Azure Synapse Analytics

Tip

Try out Data Factory in Microsoft Fabric, an all-in-one analytics solution for enterprises. Microsoft Fabric covers everything from data movement to data science, real-time analytics, business intelligence, and reporting. Learn how to start a new trial for free!

This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from HubSpot. It builds on the copy activity overview article that presents a general overview of copy activity.

Important

The HubSpot connector version 2.0 (Preview) provides improved native HubSpot support. If you are using HubSpot connector version 1.0 in your solution, please upgrade the HubSpot connector before October 22, 2025. Refer to this section for details on the difference between version 2.0 (Preview) and version 1.0.

Supported capabilities

This HubSpot connector is supported for the following capabilities:

Supported capabilities IR
Copy activity (source/-) ① ②
Lookup activity ① ②

① Azure integration runtime ② Self-hosted integration runtime

For a list of data stores that are supported as sources/sinks , see the Supported data stores table.

The service provides a built-in driver to enable connectivity, therefore you don't need to manually install any driver using this connector.

The connector supports the Windows versions in this article.

Getting started

To perform the Copy activity with a pipeline, you can use one of the following tools or SDKs:

Create a linked service to HubSpot using UI

Use the following steps to create a linked service to HubSpot in the Azure portal UI.

  1. Browse to the Manage tab in your Azure Data Factory or Synapse workspace and select Linked Services, then click New:

  2. Search for HubSpot and select the HubSpot connector.

    Select the HubSpot connector.

  3. Configure the service details, test the connection, and create the new linked service.

    Configure a linked service to HubSpot.

Connector configuration details

The following sections provide details about properties that are used to define Data Factory entities specific to HubSpot connector.

Linked service properties

The HubSpot connector now supports version 2.0 (Preview). Refer to this section to upgrade your HubSpot connector version from version 1.0. For the property details, see the corresponding sections.

Version 2.0 (Preview)

The HubSpot linked service supports the following properties when apply version 2.0 (Preview):

Property Description Required
type The type property must be set to: Hubspot Yes
version The version that you specify. The value is 2.0. Yes
clientId The client ID associated with your HubSpot application. Learn how to create an app in HubSpot from here. Yes
clientSecret The client secret associated with your HubSpot application. Mark this field as a SecureString to store it securely, or reference a secret stored in Azure Key Vault. Yes
accessToken The access token obtained when initially authenticating your OAuth integration. Learn how to get access token with your client ID and secret from here. Mark this field as a SecureString to store it securely, or reference a secret stored in Azure Key Vault. Yes
refreshToken The refresh token obtained when initially authenticating your OAuth integration. Mark this field as a SecureString to store it securely, or reference a secret stored in Azure Key Vault. Yes
connectVia The integration runtime to be used to connect to the data store. If no value is specified, the property uses the default Azure integration runtime. No

Example:

{
    "name": "HubSpotLinkedService",
    "properties": {
        "type": "Hubspot",
        "version": "2.0",
        "typeProperties": {
            "clientId" : "<clientId>",
            "clientSecret": {
                "type": "SecureString",
                "value": "<clientSecret>"
            },
            "accessToken": {
                "type": "SecureString",
                "value": "<accessToken>"
            },
            "refreshToken": {
                "type": "SecureString",
                "value": "<refreshToken>"
            }
        }
    }
}

Version 1.0

The HubSpot linked service supports the following properties when apply version 1.0:

Property Description Required
type The type property must be set to: Hubspot Yes
clientId The client ID associated with your HubSpot application. Learn how to create an app in HubSpot from here. Yes
clientSecret The client secret associated with your HubSpot application. Mark this field as a SecureString to store it securely, or reference a secret stored in Azure Key Vault. Yes
accessToken The access token obtained when initially authenticating your OAuth integration. Learn how to get access token with your client ID and secret from here. Mark this field as a SecureString to store it securely, or reference a secret stored in Azure Key Vault. Yes
refreshToken The refresh token obtained when initially authenticating your OAuth integration. Mark this field as a SecureString to store it securely, or reference a secret stored in Azure Key Vault. Yes
useEncryptedEndpoints Specifies whether the data source endpoints are encrypted using HTTPS. The default value is true. No
useHostVerification Specifies whether to require the host name in the server's certificate to match the host name of the server when connecting over TLS. The default value is true. No
usePeerVerification Specifies whether to verify the identity of the server when connecting over TLS. The default value is true. No
connectVia The integration runtime to be used to connect to the data store. If no value is specified, the property uses the default Azure integration runtime. No

Example:

{
    "name": "HubSpotLinkedService",
    "properties": {
        "type": "Hubspot",
        "typeProperties": {
            "clientId" : "<clientId>",
            "clientSecret": {
                "type": "SecureString",
                "value": "<clientSecret>"
            },
            "accessToken": {
                "type": "SecureString",
                "value": "<accessToken>"
            },
            "refreshToken": {
                "type": "SecureString",
                "value": "<refreshToken>"
            }
        }
    }
}

Dataset properties

For a full list of sections and properties available for defining datasets, see the datasets article. This section provides a list of properties supported by HubSpot dataset.

To copy data from HubSpot, set the type property of the dataset to HubspotObject. The following properties are supported:

Property Description Required
type The type property of the dataset must be set to: HubspotObject Yes
tableName Name of the table. For version 2.0 (Preview), the name of the table is <HubSpot Category>.<Sub Category>.<Object Name>, for example: CRM.Commerce.Payments. Yes for version 2.0 (Preview).
No for version 1.0 (if "query" in activity source is specified)

Example

{
    "name": "HubSpotDataset",
    "properties": {
        "type": "HubspotObject",
        "typeProperties": {},
        "schema": [],        
        "linkedServiceName": {
            "referenceName": "<HubSpot linked service name>",
            "type": "LinkedServiceReference"
        }
    }
}

Copy activity properties

For a full list of sections and properties available for defining activities, see the Pipelines article. This section provides a list of properties supported by HubSpot source.

HubspotSource as source

To copy data from HubSpot, set the source type in the copy activity to HubspotSource. The following properties are supported in the copy activity source section:

Property Description Required
type The type property of the copy activity source must be set to: HubspotSource Yes
query Use the custom SQL query to read data. For example: "SELECT * FROM Companies where Company_Id = xxx". No (if "tableName" in dataset is specified)

Note

query is not supported in version 2.0 (Preview).

Example:

"activities":[
    {
        "name": "CopyFromHubspot",
        "type": "Copy",
        "inputs": [
            {
                "referenceName": "<HubSpot input dataset name>",
                "type": "DatasetReference"
            }
        ],
        "outputs": [
            {
                "referenceName": "<output dataset name>",
                "type": "DatasetReference"
            }
        ],
        "typeProperties": {
            "source": {
                "type": "HubspotSource",
                "query": "SELECT * FROM Companies where Company_Id = xxx"
            },
            "sink": {
                "type": "<sink type>"
            }
        }
    }
]

Data type mapping for HubSpot

When you copy data from HubSpot, the following mappings apply from HubSpot's data types to the internal data types used by the service. To learn about how the copy activity maps the source schema and data type to the sink, see Schema and data type mappings.

HubSpot data type Interim service data type (for version 2.0 (Preview)) Interim service data type (for version 1.0)
bool Boolean Boolean
boolean Boolean Boolean
enumeration String String
string String String
object_coordinates String String
phone_number String String
json String String
date DateTime Not supported.
datetime DateTime DateTime
number Decimal Decimal
integer Integer Integer
object String Not supported.

Lookup activity properties

To learn details about the properties, check Lookup activity.

HubSpot connector lifecycle and upgrade

The following table shows the release stage and change logs for different versions of the HubSpot connector:

Version Release stage Change log
Version 1.0 End of support announced /
Version 2.0 (Preview) Public Preview • The tableName value is <HubSpot Category>.<Sub Category>.<Object Name>, for example: CRM.Commerce.Payments.

• date is read as DateTime data type.

• object is read as String data type.

useEncryptedEndpoints, useHostVerification, usePeerVerification are not supported in the linked service.

query is not supported.

Upgrade the HubSpot connector from version 1.0 to version 2.0 (Preview)

  1. In Edit linked service page, select version 2.0 (Preview) and configure the linked service by referring to Linked service properties version 2.0 (Preview).

  2. The data type mapping for the HubSpot linked service version 2.0 (Preview) is different from that for the version 1.0. To learn the latest data type mapping, see Data type mapping for HubSpot.

  3. query is only supported in version 1.0. You should use the tableName instead of query in version 2.0 (Preview).

For a list of data stores supported as sources and sinks by the copy activity, see supported data stores.