
Table of contents
HubSpot Engagement
Engagement activity covers the interaction types logged on HubSpot records: emails, calls, meetings, tasks and notes. When a mapped user creates an engagement in HubSpot, WorkSights receives it and displays it on the timeline in sequence with other activity.
For connection steps, see HubSpot Setup.
What WorkSights Receives
WorkSights captures logged emails, inbound and outbound calls, meetings, tasks and notes created on any HubSpot CRM record. Each engagement includes the title or subject, the timestamp, and the associated contact, company, deal or ticket.
For emails, WorkSights also parses participant information from the email headers, so the activity shows who was on the email. No other engagement type includes participant records.
Full email bodies, call recordings and note bodies are never received. WorkSights captures engagement metadata only.
How It Appears in WorkSights
Each engagement type maps to a WorkSights category. Emails are categorized as Email. Meetings and calls are categorized as Calendar Change. Tasks are categorized as Task. Notes are categorized as General.
Activity titles include the associated contact name when available. Examples: John Smith: Re: Meeting next week for an email, Meeting regarding John Smith for a meeting, John Smith: Follow up on proposal for a task.
Engagements are linked to their associated contacts and companies in ClientSights automatically, so client relationship context builds as your team works.
Engagements are included in the first-connect backfill. For the first 7 days after connecting, WorkSights sweeps the previous 30 days of engagement activity, so recent history fills in on its own.
Troubleshooting
Engagement activity is not appearing
Confirm the affected user is mapped in the Users tab and that Engagement is enabled in the Features tab. The backfill covers the 30 days before connection and runs during the first 7 days, so older engagements do not appear.
Email participants are missing
Participants are parsed from email headers. If HubSpot did not include headers in the payload, the activity appears without participant detail.
Activity is delayed
This is expected. Activity is processed in batches about every 20 minutes. The hourly sweep covers CRM objects but not engagements, so after the first 7 days engagement activity relies on webhook delivery.