HubSpot signals
Start with the HubSpot integration setup guide if you have not connected HubSpot yet.
Vaam sends prospect interactions to HubSpot as timeline events. These include a video view, a completed sequence, an accepted LinkedIn connection, and a click on a tracked link. The event appears on the matching contact and, in some cases, the company. Use these events to trigger HubSpot workflows that route leads, alert reps, change deal stages, or start plays. This page lists each signal, its payload, and common workflow patterns.
How signals appear in HubSpot
Section titled “How signals appear in HubSpot”Vaam writes each event as a timeline event on the matched contact. If Vaam can identify an anonymous video viewer only by company domain, the event appears on the company timeline instead.
Vaam provides a HubSpot event template for each signal. You do not need to create or configure the templates. Each template has tokens such as sequence name, video title, completion percentage, and message body. Vaam fills these tokens for every event so you can read them in HubSpot and use them in workflow conditions.
To use a signal, create a contact-based or company-based workflow. Select “Contact has timeline event” or “Company has timeline event” as the workflow trigger, then choose the relevant Vaam template.
Signal catalog
Section titled “Signal catalog”Video engagement from shared videos
Section titled “Video engagement from shared videos”These signals fire when someone interacts with a Vaam video share link. The link can be in an email, chat, or thread outside a Vaam sequence.
Vaam Video Opened
Section titled “Vaam Video Opened”Someone clicked the share link, and the video page loaded.
What you get: video title.
Use it for: first-touch alerts or as a precondition for follow-up tasks. It is the earliest signal that a recipient is engaging.
Vaam Video Viewed
Section titled “Vaam Video Viewed”The recipient pressed play and started watching.
What you get: video title.
Use it for: warm-lead routing. This shows stronger intent than Opened because the prospect chose to consume the content.
Vaam Video Conversion
Section titled “Vaam Video Conversion”The recipient took the call to action by clicking the CTA button, booking a meeting, or submitting a form attached to the video.
What you get: video title, conversion type description (which CTA fired).
Use it for: immediate rep alerts. This is the highest-intent signal in this group.
For all three video signals, anonymous viewers identified only by company domain produce a company-timeline event instead of a contact-timeline event. Build company-level workflows to capture these events.
Sequence lifecycle
Section titled “Sequence lifecycle”These signals mark the start, finish, and stop of a prospect’s journey through a Vaam sequence.
Sequence Started
Section titled “Sequence Started”A prospect was added to a sequence, and the sequence is now running for them.
What you get: sequence name, link to the prospect’s sequence activity in Vaam.
Use it for: stamping lifecycle stage, logging the touch in your reporting, or starting pre-outreach research tasks.
Sequence Completed
Section titled “Sequence Completed”Every step of the sequence ran to its end without being canceled.
What you get: sequence name, link to the prospect’s sequence activity.
Use it for: nurture flows for prospects who did not convert or reviews of sequence performance.
Sequence Canceled
Section titled “Sequence Canceled”The prospect’s sequence was stopped manually by a rep, by auto-reply detection, or because the prospect replied.
What you get: sequence name, link to the prospect’s sequence activity.
Use it for: routing a prospect to a different play or updating the deal stage when the prospect drops out.
Sequence step actions
Section titled “Sequence step actions”These signals fire as Vaam executes individual sequence steps and when the prospect responds.
Email Sent
Section titled “Email Sent”Vaam sent an automated email step on the prospect’s behalf.
What you get: sequence name, email body.
Use it for: reconciling sent volume with HubSpot reporting or auditing the exact copy that went out.
Email Received
Section titled “Email Received”The prospect replied to a sequence email.
What you get: sequence name.
Use it for: halting automation and handing off to a rep when a prospect replies.
LinkedIn Message Sent
Section titled “LinkedIn Message Sent”Vaam sent the LinkedIn DM step.
What you get: sequence name, message body.
Use it for: mirroring LinkedIn touches into HubSpot reporting alongside email activity.
LinkedIn Message Received
Section titled “LinkedIn Message Received”The prospect replied on LinkedIn.
What you get: sequence name, message text, link to the LinkedIn thread.
Use it for: pausing sequences, alerting reps, and logging the conversation, as you do for email replies.
LinkedIn Connection Requested
Section titled “LinkedIn Connection Requested”The connection-request step ran for the prospect.
What you get: sequence name.
Use it for: tracking top-of-funnel volume or creating a follow-up task if the request remains pending after a few days.
LinkedIn Connection Accepted
Section titled “LinkedIn Connection Accepted”The prospect accepted the connection request inside the configured window.
What you get: sequence name, the note that was sent with the original connection request, if any.
Use it for: updating lifecycle stage and adding the prospect to outreach queues. This is a strong warmth signal because the prospect explicitly opted into seeing your content.
LinkedIn Connection Not Accepted
Section titled “LinkedIn Connection Not Accepted”The connection request timed out without being accepted.
What you get: sequence name.
Use it for: segmenting unresponsive contacts for a different angle, such as a different sender, an email-only sequence, or no further outreach.
LinkedIn Profile Visited
Section titled “LinkedIn Profile Visited”Vaam ran the automatic profile-visit step.
What you get: sequence name.
Use it for: light-touch top-of-funnel tracking. It is more useful in reporting than in real-time triggers.
Sequence-embedded video signals
Section titled “Sequence-embedded video signals”These signals differ from the standalone video signals above. They fire when a prospect engages with a video embedded inside a sequence step, such as an email or LinkedIn message that includes a Vaam video.
Sequence Video Opened
Section titled “Sequence Video Opened”The prospect opened the email or message containing the embedded video.
What you get: sequence name.
Use it for: detecting when a sequence touch reached the inbox and got attention.
Sequence Video Started
Section titled “Sequence Video Started”The prospect pressed play on the embedded video.
What you get: sequence name.
Use it for: measuring clear engagement with the message. This is stronger than an open.
Sequence Video Watched 75%
Section titled “Sequence Video Watched 75%”The prospect watched at least three-quarters of the video.
What you get: sequence name, completion percentage.
Use it for: immediate routing. This is Vaam’s strongest non-conversion intent signal.
Sequence Video Conversion
Section titled “Sequence Video Conversion”The prospect took the CTA action from the in-sequence video by clicking the button, booking, or submitting.
What you get: sequence name, conversion type description.
Use it for: notifying the owner, increasing the lead score, or changing the deal stage.
Tracked links
Section titled “Tracked links”Link Clicked
Section titled “Link Clicked”The prospect clicked a tracked link inside a sequence step. This is typically an email body link that Vaam wrapped for tracking.
What you get: the destination URL.
Use it for: branching on the URL. Links to pricing, a case study, or a demo signup can trigger different actions from low-intent destinations.
Quick Forms
Section titled “Quick Forms”Quick Form Submitted
Section titled “Quick Form Submitted”The prospect submitted a Quick Form from a standalone form link, a sequence message, a video, or an embedded form.
What you get: form title, sequence name when the form came from a sequence, a link back to Vaam, and an answer summary. Answer values are redacted by default unless the form is configured to sync full answers.
Use it for: alerting the owner, updating lead score, routing the prospect, creating a task, or moving the deal to the next stage.
Learn more in Quick Forms.
Tips for building Vaam-triggered workflows
Section titled “Tips for building Vaam-triggered workflows”- Use company-level workflows when the contact may be anonymous. Vaam Video Opened, Vaam Video Viewed, and Vaam Video Conversion events can land on the company timeline if Vaam could not identify the individual viewer. A contact-only workflow will miss them.
- Combine signals with HubSpot filters such as deal stage, contact owner, lifecycle stage, and country. A 75% watch from an existing customer should route differently from one from a fresh prospect.
- Branch on tokens, not only the event. You can filter the conversion type, link URL, and sequence name tokens. Keep one workflow tidy instead of building five near-duplicates.
- Do not handle replies twice. If you have both Email Received and LinkedIn Message Received workflows, prevent conflicting actions such as two competing tasks. One “Prospect replied” workflow that listens for either signal is usually cleaner.