HubSpot is an AI-powered customer platform with all the software, integrations, and resources you need to connect your marketing, sales, and customer service.
Provide a name for the connection in Connection name.
Select Open connection metadata to define metadata for the connection when it has been created.
Click Create.
Connection settings
Setting
Description
Data gateway
Select a Data Movement gateway if required by your use case.
Information note
This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None.
Enter the date, in the format MM/DD/YYYY, from which the data must be replicated from your source to your target.
Personal Access Token
Personal access token.
Schema
Information note
Schemas and naming conventions can change from version to version. It is recommended to verify your version before continuing.
The schema and info displayed below is for version 2.
Custom HubSpot field replication
Custom object properties, or fields, are supported by HubSpot integration. It will query the properties list for each object and, if custom fields are available through HubSpot’s API, replicate them to your destination.
The data types of these fields will be the same as the data type in HubSpot. For example: A custom field containing date data will be a date field in your destination.
This is applicable to any object that supports custom fields in HubSpot.
HubSpot date/date-time values & UNIX timestamps
HubSpot uses UNIX-formatted timestamps in milliseconds to store date and datetime data. For more information, see Charts overview. It doesn’t perform any transformation during the replication process, meaning these values won’t be converted to timestamps before they’re loaded into your destination.
To account for this, consider creating a user-defined function to perform the conversion or building views on top of the raw data.
Depending on your destination, table and column names may not appear as they are outlined below.
campaigns
The campaigns table contains info about the campaigns in your HubSpot account.
The contact_lists table contains info about the contacts lists in your HubSpot account. Contact lists are used to segment contacts into groups, and there are two types: dynamic (smart lists) and static.
The contacts table contains info about individual contacts in HubSpot.
Contact properties
If properties have been set for the contact, additional fields beginning with properties__ will be included in the table. Note: Contacts will only have an entry for a property if that property has been set for the contact’s record.
Tables for custom CRM objects in your HubSpot account will have the same name as the object. For example, if you have a custom object named cars, the table will be named cars.
The fields listed below are standard fields; they are included in every custom object table. A field will be added for each property you select when configuring the table. The property names will be prefixed with property_. For example, if you have a property named model, it will appear as property_model.
The email_events table contains info about email events and how recipients interact with content.
Email events and HubSpot permissions
Replicating this table requires Super Admin permissions in HubSpot. The Super Admin role is different than the Admin role, which you can read more about in HubSpot’s documentation.
If this table is selected and you don’t have Super Admin permissions in HubSpot, an error similar to the following will surface in the integration’s Extraction Logs:
tap - ERROR b'{"status":"error","message":"This oauth-token (**********) does not have proper permissions! (requires any of [email-access])", [...]
fields: ARRAY, which is also a nested data structure.
defaultValue: STRING
description: STRING
displayOrder: INTEGER
enabled: BOOLEAN
fieldType: STRING
groupName: STRING
hidden: BOOLEAN
isSmartField: BOOLEAN
label: STRING
labelHidden: BOOLEAN
name: STRING
options: ARRAY, which is also a nested data structure.
description: STRING
displayOrder: INTEGER
doubleData: NUMBER
hidden: BOOLEAN
label: STRING
readOnly: BOOLEAN
value: STRING
placeholder: STRING
required: BOOLEAN
selectedOptions: ARRAY
type: STRING
unselectedLabel: STRING
validation: OBJECT, which is also a nested data structure.
blockedEmailAddresses: ARRAY
data: STRING
message: STRING
name: STRING
useDefaultBlockList: BOOLEAN
isSmartGroup: BOOLEAN
richText: OBJECT, which is also a nested data structure.
content: STRING
formType
STRING
guid
STRING
ignoreCurrentValues
BOOLEAN
inlineMessage
STRING
leadNurturingCampaignId
STRING
metaData
ARRAY
This is a nested data structure:
name: STRING
value: STRING
method
STRING
migratedFrom
STRING
name
STRING
notifyRecipients
STRING
performableHtml
STRING
portalId
INTEGER
redirect
STRING
submitText
STRING
tmsId
STRING
updatedAt
DATE-TIME
owners
The owners table contains info about the owners that exist in your HubSpot portal. Owners are created and updated in HubSpot when new users are added or when owners are synced from Salesforce to HubSpot.
