Send email lists to HubSpot¶
Note
This topic contains information about configuring a destination that sends query results to HubSpot using orchestrations. To configure a destination that sends audiences to HubSpot using campaigns see this topic .
HubSpot is a CRM platform built around dedicated hubs for marketing, sales, services, content management, and operations.
Use Amperity to manage contact lists in HubSpot. Build a query using the email field and send the results of that query to HubSpot. Amperity will update contacts that already exist in HubSpot; Amperity does not create contacts.
Note
Field names that are sent from Amperity to HubSpot should be lowercase and contain only letters (a-z
), numbers (0-9
), and underscores (_
). Amperity automatically converts uppercase letters to lowercase and replaces non-underscore characters (such as #
, *
, or -
) with an underscore.
Caution
Attribute fields sent to HubSpot from Amperity that contain values representing a specific day, month, and year must be represented in UTC time and can be formatted as ISO 8601 strings or as EPOCH-timestamps in milliseconds .
Important
HubSpot has specific requirements for email address validation . All email addresses that are sent to HubSpot must:
Have a valid format, as defined by RFC 2822.
May not contain quotation marks in the local part of the address, which is the part to the left of the @ symbol.
Must end in a valid top-level domain (TLD), as listed at https://data.iana.org/TLD/tlds-alpha-by-domain.txt and may contain Unicode characters within the TLD.
If a list of email addresses that is sent to HubSpot contains a single invalid email address the entire import will fail and return a 400 error.
If you experience a 400 error (due to invalid email addresses), identify which email addresses are invalid, remove them from the list, and then resend a list of valid email addresses to HubSpot.
Amperity will update contacts that already exist in HubSpot; Amperity does not create contacts.
Get details¶
Review the following details before configuring credentials for HubSpot and before configuring Amperity to send email lists to HubSpot.
![]() |
Credential settings
|
Configure credentials¶
Configure credentials for HubSpot before adding a destination.
An individual with access to HubSpot should use SnapPass to securely share “refresh token” details with the individual who will configure Amperity.
To configure credentials for HubSpot
![]() |
From the Settings page, select the Credentials tab, and then click the Add credential button. |
![]() |
In the Credentials settings dialog box, do the following: From the Plugin dropdown, select HubSpot. Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination. |
![]() |
The settings that are available for a credential are determined by the credential type. For the “hubspot” credential type, configure settings, and then click Save.
|
Add destination¶
Use a sandbox to configure a destination for HubSpot. Before promoting your changes, send a test audience, and then verify the the results in HubSpot. After the end-to-end workflow has been verified, push the destination from the sandbox to production.
To add a destination for HubSpot
![]() |
Open the Destinations page, and then click the Add destination button. ![]() To configure a destination for HubSpot, do one of the following:
|
![]() |
Select the credential for HubSpot from the Credential drop-down, and then click Continue. Tip Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to HubSpot. |
![]() |
In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination. Configure business user access By default a destination is available to all users who have permission to view personally identifiable information (PII). Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies. Enable the PII setting checkbox to allow users with limited access to PII access to this destination. Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow. |
![]() |
Configure the following settings, and then click “Save”. Audience primary key
List name (Required at orchestration)
|
![]() |
After this destination is configured, users may configure Amperity to:
to HubSpot. |