Skip to main content
CRM Integration

AI Lead Scoring for HubSpot

Your properties, your Workflows, your existing scoring. Trailspark adds Hot, Warm, or Cold scores with written reasoning on Contacts, plus propensity and buying-group coverage on the Company.

What syncs between Trailspark and HubSpot

Trailspark reads your HubSpot contacts, companies, deals, and engagement to score each account, then writes results to custom properties you create, updated after each evaluation.

HubSpot
Trailspark

HubSpot sends to Trailspark

  • From HubSpot

    Contacts & Companies

    Job title, lifecycle stage, and lead status from Contacts; industry, employee count, and revenue from Companies; plus custom properties you map. Used for ICP matching and role-based scoring.

  • From HubSpot

    Deals

    Synced onto accounts so deal history informs scoring. On by default; limit it to the pipelines you choose.

  • From HubSpot

    Engagement

    Email opens and clicks, form submissions, page views, and meeting bookings flow in as signals for scoring.

  • From HubSpot

    CRM Role Source Field

    Point Trailspark at a Contact property where your team records buying roles, and those assignments are treated as authoritative.

Trailspark writes to HubSpot

  • To HubSpot

    Trailspark Score

    Hot, Warm, or Cold, written to a Contact property you create. Updated after each evaluation.

  • To HubSpot

    Trailspark Reasoning

    The plain-language reason behind the score, in a multi-line text property reps read before they act.

  • To HubSpot

    Evaluation Date, ICP & Score Status

    When the evaluation ran, which ICP scored the contact, and whether that score is current, retired, or not evaluated, so Workflows can tell a fresh score from a stale one. ICP and status are optional.

  • To HubSpot

    Company propensity

    High, medium, or low on the Company. Contacts can take propensity as a fallback when there's no Company. Optional, mapped per property.

  • To HubSpot

    Buying-group roles & coverage

    With buying-group push on: each contact's roles, plus Company properties for buying-group stage and coverage. Only mapped properties are written.

Use cases

Run reasoned scoring next to your MQL model

Trailspark writes to its own properties, so your existing HubSpot scoring keeps running. Put the two side by side, compare them against closed-won deals, and decide what to consolidate.

Score product usage with HubSpot engagement

HubSpot sees email opens, form fills, and meetings; your product sees usage. Trailspark scores them together with the contacts, companies, and deals you sync, and writes one Hot, Warm, or Cold score with its reasoning back to the Contact.

See buying-group coverage on the Company

Buying Groups tracks who fills each role at an account. Push it to HubSpot and the Company shows its buying-group stage and coverage next to its propensity, where your Workflows can act on it.

Setup

One-click OAuth with a HubSpot admin account. No credentials to enter.

  1. 1

    Connect with OAuth

    A HubSpot admin approves the connection. Trailspark handles the OAuth app, so there's nothing to configure in HubSpot first.

  2. 2

    Map your properties

    Trailspark loads your HubSpot properties when you connect. Map the ones it reads and the custom properties that receive scores.

  3. 3

    Choose what gets written

    Pick the score levels that can create new contacts and whether buying-group properties are pushed. Everything else stays as is.

Connect HubSpot with Trailspark step by step

Our docs cover the one-click OAuth connection, the permissions Trailspark requests, what gets synced, deal sync settings, and troubleshooting.

Read the HubSpot setup guide (opens in a new tab)

How the HubSpot integration works: common questions

Custom Contact properties for Score, Evaluation Date, and Reasoning (multi-line text). ICP, Score Status, company propensity, and buying-group properties are optional. Trailspark writes only to the properties you map.

No. Record creation is off by default. Turn it on and pick the score levels that qualify, and Trailspark creates contacts only for those, associated with the matching Company.

No. Trailspark writes only to the custom properties you map, so HubSpot's score properties and its predictive scoring keep running as they did. You can run both side by side and compare before deciding what to keep.

Trailspark matches contacts by email and updates the existing record. If HubSpot has duplicates with the same email, it uses the most recently updated one.

Yes. Deal sync is on by default once HubSpot is your active CRM, and attaches deals to accounts to inform scoring. You can limit it to specific pipelines or turn it off.

No. Turn on buying-group push and map only the properties you want. Unmapped properties are never written.

Trailspark is billed on the unique accounts it evaluates each month, not seats or CRM contacts. Every plan is the full platform, Free included; see pricing for the tiers, or talk to us about custom volume.

Other integrations and pages

Salesforce

CRM · Two-way sync

Segment

Marketing and CDP · Two-way sync

AI lead scoring

Set rules in plain English, not points

See Trailspark and HubSpot on your own data.

Start free. Connect HubSpot with one-click OAuth and watch scores land in custom properties on the contacts your reps already use.