Table of contents
HubSpot Integration Overview
The HubSpot integration brings CRM, sales, service, and engagement activity into the WorkSights timeline. When mapped users create or update records in HubSpot, WorkSights receives those events and displays them as structured entries. HubSpot contacts and companies are also bridged into ClientSights as Person and Company records, so leaders can see relationship context alongside team activity.
For connection steps, see HubSpot Setup.
What WorkSights Receives
CRM
Contact and company creation and field updates. Contacts are bridged to ClientSights Person records and companies to ClientSights Company records.
Sales
Deal creation, stage changes, amount updates, and close date changes.
Service
Ticket creation and status, priority, and pipeline changes.
Engagement
Emails logged in HubSpot, calls, meetings, tasks, and notes. WorkSights receives engagement metadata: titles, participants, timestamps, and associations to contacts, companies, deals, or tickets. Full email bodies, call recordings, and note bodies are never received.
How HubSpot Activity Appears
HubSpot activity appears across several categories depending on the record type. Contact, company, deal, and ticket property changes are categorized as General. Meetings and calls are categorized as Calendar Change. Emails are categorized as Email. Tasks are categorized as Task. Tickets use the Ticket category.
When a user edits multiple fields on the same record within a 10-minute window, WorkSights consolidates them into a single activity entry rather than creating a separate entry for each change. The activity detail lists each change on its own line. Changes that happen more than 10 minutes apart generate separate entries.
Activity appears within roughly 20 minutes of occurring. HubSpot is one of the few integrations with a second ingestion channel: an hourly delta sweep runs alongside real-time webhooks to catch anything that wasn’t delivered. This means HubSpot activity is more reliably complete than webhook-only integrations.
Bulk imports from HubSpot, such as CSV uploads, are automatically filtered and will not appear on the timeline.
ClientSights
HubSpot is one of the strongest ClientSights signal sources. Contacts resolve to Person records and companies resolve to Company records. Deals, tickets, and engagements walk HubSpot’s own association model to link activity to the relevant Person and Company records. This means relationship context builds automatically as your team works in HubSpot, without any manual tagging.
Contacts and companies are bridged into ClientSights even when no mapped WorkSights user owns the record. Timeline activity, however, only appears for mapped and subscribed users.
Integration Page Overview
The HubSpot integration page contains four tabs:
- Overview - Connection details and integration owner
- Users - HubSpot accounts matched to WorkSights users by email
- Features - Visibility controls for CRM, Sales, Service, and Engagement
- Connections - Connected HubSpot accounts
Troubleshooting
No activity appearing
Confirm the affected user is mapped by email in the Users tab. Confirm the relevant feature area is enabled in the Features tab. HubSpot activity requires both a mapped user and an active feature subscription.
Activity is delayed
This is expected. Activity is processed in batches roughly every 20 minutes. The hourly delta sweep also runs at 23 minutes past the hour to catch anything webhooks missed. Allow up to an hour before treating delayed activity as missing.
Too many activities on the record
Consolidation merges changes within a 10-minute window per record and user. Changes that occur more than 10 minutes apart generate separate entries. This is expected behavior.
Activity shows “unknown contact”
HubSpot may not have linked the engagement or deal to a contact. The activity still appears, but without a contact association.
Bulk import activity appearing
This should not happen. Bulk import events are filtered automatically. If import activity appears, contact us at success@worksights.ai or via the in-app form.