Skip to main content

​
Overview

The HubSpot integration does three jobs: it creates accounts automatically when deals reach the stage you pick, it gives agents scoped read access to deals, companies, and contacts for context, and it serves as a verification source — a guide can close an outcome on a fresh read of the customer’s HubSpot record. The connection is org-wide: one HubSpot portal per Thread organization, connected once by an admin.

​
Benefits

Auto-Create Accounts

Deals move to “Closed Won” → Accounts created automatically

No Manual Entry

Customer data flows from HubSpot to Thread automatically

Verified Outcomes

Guides close outcomes on a fresh read of the HubSpot record

Rich Context

Deals, notes, and files power AI drafting and agent decisions

​
Setup Instructions

​
Prerequisites

  • HubSpot Sales Hub (Professional or Enterprise recommended)
  • Admin or Super Admin permissions in HubSpot
  • Thread account with admin role
Thread connects one CRM at a time — HubSpot, Salesforce, or Notion in CRM mode. Disconnect the other CRM first if you’re switching.

​
Step 1: Connect OAuth

1

Navigate to Connectors

In Thread: Connectors → Find HubSpot → Click “Connect”
2

Authorize Thread

Redirected to HubSpot → Login if needed → Review permissions → Click “Grant access”Permissions requested:
  • Read deals (to fetch deal data)
  • Read companies (for company info)
  • Read contacts (for customer contacts)
  • Read notes (for context)
3

Confirm Connection

Redirected back to Thread → Green checkmark appears → Status: “Connected”

​
Step 2: Pick the Trigger Stage

1

Select Pipeline

The setup flow lists your HubSpot pipelines — pick the one your closed deals live in.
2

Select Deal Stage

Choose which stage triggers account creation — “Closed Won” is the common pick. When a deal reaches this stage, Thread creates the account.
3

Test with Sample Deal

Create a test deal in HubSpot:
  1. Set stage to your configured trigger stage
  2. Wait 1-2 minutes
  3. Check Thread for the new account
  4. Verify the data mapped correctly
  5. Delete the test account if successful

​
How It Works

​
Webhook Flow

​
Guide Verification

HubSpot is the guide gallery’s record check. When you enroll a customer with a guide, you bind the guide to that customer’s HubSpot record — and from then on:
  • The guide sees that one record, chosen at enroll. The scope is the guardrail; there’s nothing else to configure.
  • When the guide believes the outcome is reached, it takes a fresh read of the record. The read lands in the watch log as a receipt, and the outcome shows as “Done — verified (HubSpot record).”
  • What “done” means stays in your instructions — the tool only reports what the record says.
See Outcomes and verification. Motion milestone checks can also consult HubSpot reads as evidence — see Milestones and verification.

​
Use Cases

​
1. Sales-to-Success Handover

Workflow:
  • AE closes the deal in HubSpot
  • Thread creates the account automatically
  • AI drafts Handover Brief answers from CRM notes
  • AE reviews and enriches the brief
  • The account routes into your workflow or Motion

​
2. Agent Context

Connected agents get read-only HubSpot tools scoped to the account they’re working: the deal (with pipeline and stage), the company, contacts, deal notes and associations, files on the deal, owner lookup, and custom-field discovery. Agents never pick which account’s records they touch — the account in context resolves it. Deal writes (create/update) are approval-gated like every state-changing action.

​
3. Context for AI

CRM data powers:
  • Handover Brief drafting
  • Email personalization
  • Use case identification
  • Risk detection
  • Stakeholder mapping

​
Field Mappings

​
Standard Mappings

Beyond the standard fields, the full deal payload rides along as AI context — industry, company size, use-case notes, and custom properties all inform Handover Brief drafts and agent work without per-field mapping.

​
Troubleshooting

​
”Account Not Created”

Problem: Deal closed but no account in Thread Possible causes:
  1. Wrong deal stage (not the configured trigger)
  2. Wrong pipeline (the trigger is pipeline-specific)
  3. Webhook not received
Solutions:
  • Verify the deal’s pipeline and stage match the configuration
  • Check HubSpot webhook logs
  • Ensure the deal has a company, amount, and close date

​
”Duplicate Accounts Created”

Problem: Same customer has multiple accounts Possible causes:
  1. Deal stage changed multiple times
  2. Manual account also created
  3. Company name variations
Solutions:
  • Configure to only trigger once per deal
  • Merge duplicate accounts
  • Standardize company names in HubSpot

​
”Missing Data in Account”

Problem: Account created but fields empty Possible causes:
  1. Fields not mapped
  2. Data not in HubSpot
  3. Permissions issue
Solutions:
  • Check field mappings
  • Verify data exists in HubSpot deal
  • Reconnect with full permissions
  • Manually populate critical fields

​
Best Practices

Clean CRM Data First

Standardize company names, formats, and fields before connecting

Test Thoroughly

Create 3-5 test deals to verify mappings work correctly

Document Workflow

Train AEs on the new automated handover process

Monitor Initially

Check first 10-20 auto-created accounts for issues

Use Deal Notes

Rich notes in HubSpot → Better Handover Brief drafts

Standard Naming

Consistent deal/company naming improves matching

​
Next Steps

Outcomes and verification

How the HubSpot record check closes a guide’s outcome

Handover Briefs

How HubSpot data drafts the AE-reviewed brief

Building workflows

Route auto-created accounts down the right path

Slack Integration

Connect Slack for customer channels and delivery