Hubspot Data Targets

Overview

DataBlend supports the following data targets for creating and modifying records in HubSpot.

Associations
Calls
Communications
Companies
Contacts
Custom Objects
Deals
Discounts
Emails
Files
Invoices
Line Items
Notes
Meetings
Postal Mail
Products
Quotes
Secondary Email
Tasks
Tickets

Configuration

Setting	Required/ Optional	Description
Query	Required	Select the query that will generate the data for this target. See the relevant target type documentation for additional details on what query columns are required for your target.
Query Mode	Required	Choose New unless you have a reason for choosing Latest or Specific.
Credential	Required	Select a Hubspot Credential from the list.
Object Type	Required	Choose the Hubspot Collector type from the drop-down menu.
Update	Optional	Keep toggled off to Create. Toggle on to Update.
Action	Required	Select from the pre-populated drop-down selections.
Batch Size	Optional	Number of records sent to HubSpot per request (1-100). Lower this if large batches fail with a 500 error. Defaults to 100.

To learn more about HubSpot API requirements, please visit HubSpot APIs | Getting started.

Advanced

History Retention

History Retention (Days) allows users to decide how long they want the information from their data targets to be stored. This field is optional.

Timeout (seconds)

The Timeout section allows users to determine if they would like to timeout collections taking longer than a set number of seconds to collect data.

Skip If No Records Found

The “Skip if No Records Found” button is used to eliminate sending information to Data Targets unnecessarily. Simply enable the “Skip if No Records Found” toggle. The use of this toggle is optional.

Agent

The Agent drop-down for users to select any agent they have established. This is optional.

Run As

Run As allows users to select from a drop-down list of users to run the Workflow. This is optional. Please note that Run As is only available to Admin users. If a user is set as the Run As and then demoted to a Member, the user which demoted the Run As user will instead be set as the Run As.