HubSpot

HubSpot connects as a company-scoped connector via OAuth. The admin authorises once; the HubSpot connector syncs structured CRM data into the entity graph on a configurable interval.

What syncs

HubSpot yields event data only — the event materializer translates each CRM object change into an entity update:

• Contacts — become external_contact entities. Properties (email, phone, company, lifecycle stage) flow into entity properties.
• Companies — become external_relationship entities. Properties (domain, industry, revenue) flow into entity properties.
• Deals — become deal entities linked to the contact and company. Stage changes, close dates, and amounts flow through.
• Activities — notes, calls, and meetings logged in HubSpot become activity signals on the contact’s profile page.

Situation detection

HubSpot is a particularly rich source for property-based situation detection. Examples you might configure:

• Deal stage hasn’t changed in 21 days and expected close is within 30.
• Contact’s last activity was over 45 days ago and lifecycle stage is “customer.”
• New company created with industry matching an active outreach campaign.

Write-back

HubSpot write-back is not currently supported. The connector is read-only — updates to deals, contacts, or activities happen in HubSpot’s UI. Write-back for deal-stage updates and activity logging is planned.

Identity resolution

Contacts synced from HubSpot are matched against existing person entities using weighted identity resolution (email, phone, domain, embedding similarity). The same customer present in HubSpot, Gmail, and Stripe resolves to a single entity with all signals combined.