Skip to content
/
Hubspot Export Integratio...
Last updated

Hubspot Export Integration

Learn more about HubSpot Import Integration.

You can export data directly from Treasure Data into your HubSpot Marketing Cloud. HubSpot is an AI-powered customer platform with software, integrations, and resources you need to connect your marketing, sales, and customer service.

Prerequisites

  • Basic knowledge of Treasure Data, including the toolbelt.
  • A HubSpot account that can grant permissions to Treasure Data.

Limitation

A company record duplication occurs when sending a null company_id repeatedly. If you specify the creation of a record instead of allowing for data skipping, a NULL company_id or a non-existent company_id on HubSpot causes the company records to be created with a new company_id on HubSpot. If you rerun the same query on the same result set, duplicated records will appear.

To resolve this limitation, ingest the company_id values and de-duplicate the existing records in Treasure Data to reduce these duplications before the next run.

Static IP Address of Treasure Data Integration

If your security policy requires IP whitelisting, you must add Treasure Data's IP addresses to your allowlist to ensure a successful connection.

Please find the complete list of static IP addresses, organized by region, at the following link:
https://api-docs.treasuredata.com/en/overview/ip-addresses-integrations-result-workers/

Required Hubspot Settings

You must turn on the setting Automatically create and associate companies with contacts in HubSpot portal to enable the contacts to automatically be associated with the company.

If you turn off the bulk insert/update feature, you must create contacts using the target Contacts first. Each company’s data is created automatically, whether the setting Automatically create and associate companies with contacts in the HubSpot portal is on or off.

For more details, go to the Create or update a group of the contacts page.

Create a New Authentication

In Treasure Data, you must create and configure the data connection, to be used during export, prior to running your query. As part of the data connection, you provide authentication to access the integration.

  1. Open TD Console.

  2. Navigate to Integrations Hub >  Catalog

  3. Search for and select Hubspot.

The following dialog opens.

  1. Select Click here to connect to a new account.

You are redirected to Hubspot to log in, if you haven't logged in yet, or to the consent page to grant access to Treasure Data.

After you grant access to Treasure Data you are redirected back to TD Console.

  1. Navigate to Integrations Hub > Catalog.

  2. Select Hubspot again.

  3. The New Authentication dialog opens.

  4. Select the OAuth connection with your account name in the dropdown list.

  5. Select Continue.

  6. Name the connection.

  7. Select Done.

Define your Query

  1. Complete the instructions in Creating a Destination Integration.
  2. Navigate to Data Workbench > Queries.
  3. Select a query for which you would like to export data.
  4. Run the query to validate the result set.
  5. Select Export Results.
  6. Select an existing integration authentication.
  7. Define any additional Export Results details. In your export integration content review the integration parameters. For example, your Export Results screen might be different, or you might not have additional details to fill out:
  8. Select Done.
  9. Run your query.
  10. Validate that your data moved to the destination you specified.

Integration Parameters for Hubspot

Depending on what you select for your destination, the parameters vary. The table here lists all possible parameters.

Edit the following parameters and select Done.

The following table describes the integration parameters for HubSpot export:

CLI ParameterParameter TypeSample ValueUI DescriptionExplanationRequired Column(s)

target

Enum (contacts, companies, company_properties, contact_properties, contact_list)

contacts

Destination

Choose the HubSpot object to create or update:

  • contacts: create or update individual contacts.
  • contact_properties: update batches of contact properties; optionally enable batch insert.
  • companies: create or update companies using company_id or website; optionally skip missing company IDs.
  • company_properties: update batches of company properties.
  • contact_list: create or update contacts in batch and manage their membership in a static list.

contacts: email

contact_properties: email, name, value (type, fieldType for new properties)

companies: company_id or website

company_properties: email, name, value (type, fieldType for new properties)

contact_list: email

resolution_modeEnum (ignore, create)ignoreNon-existing CompanyID ResolutionSpecify how to handle rows where company_id does not exist in HubSpot.
enable_batchBooleanfalseEnable batch insertWhen exporting contact properties, toggle to insert or update records in a batch. Any row-level error stops the batch.
skip_creating_companyBooleanfalseSkip creating companies by email domainPrevent automatic company creation from a contact's email domain.
list_nameStringhubspot_listList NameRequired when target is contact_list; provide the HubSpot list name.
contact_list_actionEnum (add, remove)addActionRequired when target is contact_list; choose whether to add contacts to or remove contacts from the list.
retry_limitInteger3Retry Limit (optional)Maximum number of retries before the export stops.
retry_initial_wait_msecInteger10000Initial retry time wait in milliseconds (optional)Delay between the first and second attempts.
max_retry_wait_msecInteger300000Max retry wait in milliseconds (optional)Delay between the second and subsequent attempts.

This feature requires additional HubSpot API scope. Re-create your authentication if it was created before October 2, 2024.

When contact_list_action is set to add, the connector creates the list automatically if it does not exist. remove only detaches contacts from the list; it does not delete them.

The connector uses HubSpot upsert APIs. If a contact exists and the provided property value differs from the current value, HubSpot updates the property. Ensure your query only includes the properties you intend to update; otherwise, a new contact may be created.

Example Query

Create new contacts

select 'test@edm.com' as EMAIL, 'tester' as firstname, 'll' as lastname, '650-000-1234' as phone, 'test' as address,
'a' as city, 'CA' as state, '60599' as zip

Update a contact property

-- update value of firstname
select 'firstname' as name, 'test1@samplecom.com' as email, 'newContactName' as value

Create new Company

select '1234567890' as company_id, 'www.testwebsite.com' as website

Update a Company Property

-- update value of name
select '1234567890' as company_id, 'name' as name, 'www.google.com' as website, 'NewCompanyName' as value

Create/update contacts and add to a List

select 'test@edm.com' as EMAIL, 'Jonh' as firstname, 'Doe' as lastname, '650-000-1234' as phone, 'test' as address, 'a' as city, 'CA' as state, '60599' as zip

The property name as query column or alias (e.g. firstname, lastname) has to match with a valid contact's property defined by Hubspot. See Contact's Default Properties for more details, please note that you would need to pass the "Internal Name" of a property as column name or alias. To get that, visit Properties Management. For example, field "First name" has Internal Name as "firstname", this should be use as column name or alias in your query result.

Activate a Segment in Audience Studio

You can also send segment data to the target platform by creating an activation in the Audience Studio.

  1. Navigate to Audience Studio.
  2. Select a parent segment.
  3. Open the target segment, right-mouse click, and then select Create Activation.
  4. In the Details panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
  5. Customize the activation output in the Output Mapping panel.

  • Attribute Columns
    • Select Export All Columns to export all columns without making any changes.
    • Select + Add Columns to add specific columns for the export. The Output Column Name pre-populates with the same Source column name. You can update the Output Column Name. Continue to select + Add Columnsto add new columns for your activation output.
  • String Builder
    • + Add string to create strings for export. Select from the following values:
      • String: Choose any value; use text to create a custom value.
      • Timestamp: The date and time of the export.
      • Segment Id: The segment ID number.
      • Segment Name: The segment name.
      • Audience Id: The parent segment number.
  1. Set a Schedule.

  • Select the values to define your schedule and optionally include email notifications.
  1. Select Create.

If you need to create an activation for a batch journey, review Creating a Batch Journey Activation.

(Optional) Schedule Query Export Jobs

You can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.

Treasure Data's scheduler feature supports periodic query execution to achieve high availability.

When two specifications provide conflicting schedule specifications, the specification requesting to execute more often is followed while the other schedule specification is ignored.

For example, if the cron schedule is '0 0 1 * 1', then the 'day of month' specification and 'day of week' are discordant because the former specification requires it to run every first day of each month at midnight (00:00), while the latter specification requires it to run every Monday at midnight (00:00). The latter specification is followed.

Scheduling your Job Using TD Console

  1. Navigate to Data Workbench > Queries

  2. Create a new query or select an existing query.

  3. Next to Schedule, select None.

  4. In the drop-down, select one of the following schedule options:

    Drop-down ValueDescription
    Custom cron...Review Custom cron... details.
    @daily (midnight)Run once a day at midnight (00:00 am) in the specified time zone.
    @hourly (:00)Run every hour at 00 minutes.
    NoneNo schedule.

Custom cron... Details

Cron ValueDescription
0 * * * *Run once an hour.
0 0 * * *Run once a day at midnight.
0 0 1 * *Run once a month at midnight on the morning of the first day of the month.
""Create a job that has no scheduled run time.
 *    *    *    *    *
 -    -    -    -    -
 |    |    |    |    |
 |    |    |    |    +----- day of week (0 - 6) (Sunday=0)
 |    |    |    +---------- month (1 - 12)
 |    |    +--------------- day of month (1 - 31)
 |    +-------------------- hour (0 - 23)
 +------------------------- min (0 - 59)

The following named entries can be used:

  • Day of Week: sun, mon, tue, wed, thu, fri, sat.
  • Month: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec.

A single space is required between each field. The values for each field can be composed of:

Field ValueExampleExample Description
A single value, within the limits displayed above for each field.
A wildcard '*' to indicate no restriction based on the field.'0 0 1 * *'Configures the schedule to run at midnight (00:00) on the first day of each month.
A range '2-5', indicating the range of accepted values for the field.'0 0 1-10 * *'Configures the schedule to run at midnight (00:00) on the first 10 days of each month.
A list of comma-separated values '2,3,4,5', indicating the list of accepted values for the field.0 0 1,11,21 * *'Configures the schedule to run at midnight (00:00) every 1st, 11th, and 21st day of each month.
A periodicity indicator '*/5' to express how often based on the field's valid range of values a schedule is allowed to run.'30 */2 1 * *'Configures the schedule to run on the 1st of every month, every 2 hours starting at 00:30. '0 0 */5 * *' configures the schedule to run at midnight (00:00) every 5 days starting on the 5th of each month.
A comma-separated list of any of the above except the '*' wildcard is also supported '2,*/5,8-10'.'0 0 5,*/10,25 * *'Configures the schedule to run at midnight (00:00) every 5th, 10th, 20th, and 25th day of each month.
  1. (Optional) You can delay the start time of a query by enabling the Delay execution.

Execute the Query

Save the query with a name and run, or just run the query. Upon successful completion of the query, the query result is automatically imported to the specified container destination.

Scheduled jobs that continuously fail due to configuration errors may be disabled on the system side after several notifications.

Optionally Configure Export Results in Workflow

Within Treasure Workflow, you can specify the use of this data connector to export data.

Learn more at Using Workflows to Export Data with the TD Toolbelt.

Previous page
Next page