Below you will find necessary information how to get started with the Hubspot integration.
You will need administrator permissions to your Hubspot account to perform oAuth authorization. Make sure you have the correct access before proceeding.
Credentials & Actionsand complete the authorization flow:
There are 4 sections of settings which you can configure depending on what kind of synchronization you need.
Hull User Attributesare updated/created on
Hubspot Contact Propertieswe will use to identify
Hubspot Contact Propertiesare stored in
Hull User Attributes
Hull Account Attributesare updated/created on
Hubspot Company(see below how the linking is performed)
Hubspot Company Propertieswe will use to identify
Hubspot Company Propertiesare stored in
Hull Account Attributes
Hull Accountdepending on
The Hubspot connector allows you to synchronize data between Hull and Hubspot for the following objects:
|Hull Entity||Hubspot Entity|
No other objects besides the ones listed above are supported. If you need to synchronize additional objects please reach out to our customer success team to explore the options on a case-by-case basis.
Accounts synchronization is disabled by default. To enable it you need to setup fetch accounts and outgoing account segments settings (look above).
The Hubspot connector uses upsert policies for synchronizing data. If we cannot find a matching record, a new one will be created automatically. This section explains how we match existing records between both systems.
When synchronizing a Hull user to a
Hubspot Contact we match both by email. If the outgoing
Hull User does not have an email address, the synchronization is skipped.
When synchronizing a
Hull Account to a
Hubspot Company we match both by domain. If the account does not have a domain, the synchronization is skipped.
When synchronizing a
Hubspot Contact to a Hull user, by default we match both by email. If the contact doesn’t have an email, the synchronization is skipped. This behavior can be adjusted using incoming user identity setting.
When synchronizing a
Hubspot Company to
Hull Account, we match the account based on your configured strategy. By default, we match both by domain and we skip synchronization if
Hubspot Company does not have uit.
When adding more identifiers e.g.
external_id, you can declare if the identifier as required. If required we will skip synchronization for companies which do not satisfy this condition.
IMPORTANT: Skip behavior is changed when incoming user linking setting is turned on.
The Hubspot connector receives updates to
Hull Users and
Accounts near real-time and makes requests to the Hubspot API. The data synchronization maps the default attributes to Hubspot properties according to the tables below. If you have defined custom properties in Hubspot and configured mappings, the synchronization will also contain these fields.
Additionally you can manually select
Hull Users or
Accounts and send them to the connector. This bypass segment filtering and force update of
Hubspot Contacts and
When the Hubspot connector process update on a
Hull User profile and: 1. the outgoing user linking setting is turned on 2. the
Hull User is linked to an
Account 3. linked
Hull Account was already synchornized to
Hubspot Company (we know the Hubspot identifier)
it will associate the
Hubspot Contact with
The Hubspot connector is built with a sync component, which means we’ll make requests to API on your behalf on a 5 minute interval to fetch the latest data into Hull. In the initial sync, we will fetch all the Hubspot objects (and their corresponding properties) according to the tables below. The data will be written into a separate attribute group hubspot on the respective Hull profile, corresponding to the mapping schema you have defined.
When the Hubspot connector fetch a
Hubspot Contact and: 1. the incoming user linking setting is turned on 2. the
Hubspot Contact was associated with a
Company 3. the
Hubspot Contact satisfy the incoming identity resolution
it will try to link the stored
Hull User with appropriate
This mean it will create an empty Hull Account which will be only filled in with Hubspot Company data if the Company itself satisfies the incoming identity requirements. If not the Hull User will be linked to an empty Hull Account.
Mappings define the attributes of Hull profiles we synchronize with properties of Hubspot. In user and account profiles, the synchronized properties will show under the attribute group hubspot.
< TODO: INSERT TABLES FOR DEFAULTS >
check identifiers for accounts
Check your connector logs for any
incoming.job.error. If you see any with
Permission error go to the
Credentials Tab and perform the oAuth flow authorization again using the
Start over button. Make sure that you are linking the connector again to the same Hubspot portal. Changing the portal on once installed connector can lead to data corruption. This operation does not reset any settings from the connector. Right after it’s done the incoming dataflow should be resumed. You can verify that by searching for any
incoming.account.success log lines (it can take around 5 minutes to show up). To fill in any missing data you can use
Fetch all Contacts and
Fetch all Companies buttons on the connector tab.
fetch companies or contacts or send them via batch
mark identifiers required
duplicate property valueerror
If you see
duplicate property value error in your
outgoing.account.error logs it means that you have duplicate entry in your outgoing attribute mapping. You can inspect
hubspotWriteContact param in the log line to see the exact payload the connector tried to sent to Hubspot and failed. Search for any property name which appears there twice. Then remove the extra entry in the attributes mapper and resend the affected users/accounts via send to operation. If you want to achieve fallback strategy for outgoing attributes you need to prepare the value using Processor.