HubSpot Destination

Overview

The HubSpot destination writes evaluation results to your HubSpot Contact and Company objects. TrailSpark maps scores, reasoning, and evaluation dates to custom properties you define in HubSpot.

Prerequisites

  • HubSpot integration connected (Settings > CRM Integration > Connect tab)
  • Custom properties created in HubSpot for TrailSpark data
  • Admin or Owner role in TrailSpark
  • HubSpot admin access to create properties

Custom Properties in HubSpot

Create these custom properties on the Contact object:

Property LabelSuggested Internal NameField Type
TrailSpark Scoretrailspark_scoreSingle-line text (values: hot, warm, cold)
TrailSpark Evaluation Datetrailspark_evaluation_dateDate picker
TrailSpark Reasoningtrailspark_reasoningMulti-line text

For company propensity, create on the Company object:

Property LabelSuggested Internal NameField Type
TrailSpark Propensitytrailspark_propensitySingle-line text (values: high_propensity, medium_propensity, low_propensity)
Create a "TrailSpark" property group in HubSpot to keep all TrailSpark properties organized together.

Configuration

Go to Settings > CRM Integration > Destinations tab.

Destination Settings

  • Send Evaluations to HubSpot -- Toggle to enable/disable the destination
  • HubSpot Integration -- Select which connected HubSpot instance to use
  • Create Records if Not Found -- When enabled, creates new Contact records if no match exists. Filter by score level (Hot, Warm, Cold)

Contact Field Mapping

Map three fields to HubSpot Contact properties:

TrailSpark FieldDescription
Score FieldWhere the evaluation score is stored
Evaluation Date FieldWhere the evaluation timestamp is stored
Reasoning FieldWhere the AI reasoning is stored

TrailSpark loads your HubSpot property metadata automatically. Select properties from the dropdown. If a previously mapped property no longer exists in HubSpot, the field resets to blank.

Company Propensity Score

The propensity score card configures where account-level propensity (high/medium/low) is written:

  • Company Propensity Field (primary) -- Written to the Company object when a linked Company exists
  • Contact Propensity Field (fallback) -- Written to the Contact object when no Company is linked

Both fields are optional.

Troubleshooting

IssueResolution
Property not in dropdownVerify the property exists on the Contact object and the internal name is correct
Data not writingCheck that the destination is enabled and integration is still connected
Contact not foundTrailSpark matches by email address -- ensure the contact exists in HubSpot

Next Steps