HubSpot signals
New here? Start with the HubSpot integration setup guide.
Every meaningful prospect interaction in Vaam — a video viewed, a sequence completed, a LinkedIn connection accepted, a tracked link clicked — lands in HubSpot as a timeline event on the matching contact (and sometimes on the company). Build HubSpot workflows that trigger on these timeline events to react in real time: route hot leads, alert reps, change deal stages, kick off plays. This page lists every signal Vaam emits, what’s in the payload, and shows recipes for the most common workflow patterns.
How Vaam signals appear in HubSpot
Section titled “How Vaam signals appear in HubSpot”Vaam writes each event as a timeline event on the matched contact. For anonymous video viewers that we can only identify by company domain, the event lands on the company timeline instead.
Each signal has its own HubSpot event template that Vaam ships with the integration — you don’t need to create or configure anything. The template comes with tokens (sequence name, video title, completion percentage, message body, etc.) that are filled in for every event so you can read them in HubSpot and reference them in workflow conditions.
To use a signal in a workflow, create a contact-based or company-based workflow and pick “Contact has timeline event” (or “Company has timeline event”) as the enrollment trigger, then choose the relevant Vaam template from the list.
Signal catalog
Section titled “Signal catalog”Video engagement (standalone shared videos)
Section titled “Video engagement (standalone shared videos)”These fire when someone interacts with a Vaam video share link — a video sent over email, chat, or pasted into a thread, outside of 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.
Why workflow on it: earliest signal that a recipient is engaging. Useful for first-touch alerts and as a pre-condition for follow-up tasks.
Vaam Video Viewed
Section titled “Vaam Video Viewed”The recipient pressed play and started watching.
What you get: video title.
Why workflow on it: stronger intent than Opened — the prospect chose to consume the content. Good for warm-lead routing.
Vaam Video Conversion
Section titled “Vaam Video Conversion”The recipient took the call-to-action: clicked the CTA button, booked a meeting, or submitted a form attached to the video.
What you get: video title, conversion type description (which CTA fired).
Why workflow on it: highest-intent signal in this group. This is the one to alert reps on instantly.
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 if you want to capture those.
Sequence lifecycle
Section titled “Sequence lifecycle”These mark the start, finish, and stop of a prospect’s journey through a Vaam sequence.
Sequence Started
Section titled “Sequence Started”A prospect was enrolled and the sequence is now running for them.
What you get: sequence name, link to the enrollment in Vaam.
Why workflow on it: stamp lifecycle stage, log the touch in your reporting, or kick off 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 enrollment.
Why workflow on it: trigger nurture flows for prospects who didn’t convert, or close-the-loop reviews of sequence performance.
Sequence Canceled
Section titled “Sequence Canceled”The enrollment was stopped — manually by a rep, by an auto-reply detection, or because the prospect replied.
What you get: sequence name, link to the enrollment.
Why workflow on it: detect when a prospect drops out so you can route them to a different play or update deal stage.
Sequence step actions
Section titled “Sequence step actions”These fire as Vaam executes individual steps of a sequence, plus 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.
Why workflow on it: reconcile sent volume with HubSpot reporting, or audit the exact copy that went out.
Email Received
Section titled “Email Received”The prospect replied to a sequence email.
What you get: sequence name.
Why workflow on it: the canonical “stop the bots, a human is here” signal. Use it to halt automation and hand off to a rep.
LinkedIn Message Sent
Section titled “LinkedIn Message Sent”Vaam sent the LinkedIn DM step.
What you get: sequence name, message body.
Why workflow on it: mirror 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.
Why workflow on it: treat LinkedIn replies the same way you treat email replies — pause sequences, alert reps, log the conversation.
LinkedIn Connection Requested
Section titled “LinkedIn Connection Requested”The connection-request step ran for the prospect.
What you get: sequence name.
Why workflow on it: track top-of-funnel volume, or create a follow-up task if the request is still 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.
Why workflow on it: strong warmth signal — the prospect has explicitly opted into seeing your content. Update lifecycle stage, add to outreach queues.
LinkedIn Connection Not Accepted
Section titled “LinkedIn Connection Not Accepted”The connection request timed out without being accepted.
What you get: sequence name.
Why workflow on it: segment unresponsive contacts for a different angle (different sender, email-only sequence, drop entirely).
LinkedIn Profile Visited
Section titled “LinkedIn Profile Visited”Vaam ran the automatic profile-visit step.
What you get: sequence name.
Why workflow on it: light-touch top-of-funnel tracking — useful in reporting more than in real-time triggers.
Sequence-embedded video signals
Section titled “Sequence-embedded video signals”These are distinct from the standalone video signals above. They fire when a prospect engages with a video that’s embedded inside a sequence step (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.
Why workflow on it: first sign that 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.
Why workflow on it: clear engagement with the message. Stronger than 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.
Why workflow on it: the strongest non-conversion intent signal Vaam emits. Hot-lead territory — route immediately.
Sequence Video Conversion
Section titled “Sequence Video Conversion”The prospect took the CTA action from the in-sequence video — clicked the button, booked, or submitted.
What you get: sequence name, conversion type description.
Why workflow on it: sales-ready signal. Notify the owner, increment the lead score, change deal stage.
Tracked links
Section titled “Tracked links”Link Clicked
Section titled “Link Clicked”The prospect clicked a tracked link inside a sequence step (typically an email body link Vaam wrapped for tracking).
What you get: the destination URL.
Why workflow on it: specific links carry intent (pricing, case study, demo signup). Branch on the URL inside your workflow to react to high-intent destinations differently from low-intent ones.
Tips for building Vaam-triggered workflows
Section titled “Tips for building Vaam-triggered workflows”- Use company-level workflows for video signals where the contact may be anonymous. The Vaam Video Opened / Viewed / Conversion events can land on the company timeline if we couldn’t identify the individual viewer — a contact-only workflow will miss them.
- Combine signals with HubSpot filters (deal stage, contact owner, lifecycle stage, country) so automations only fire for the segment that should react. A 75% watch on an existing customer should route differently than one on a fresh prospect.
- Branch on tokens, not just the event. The conversion type token, the link URL token, and the sequence name token are all filterable. Use them to keep one workflow tidy instead of building five near-duplicates.
- Don’t double-handle replies. If you have both Email Received and LinkedIn Message Received workflows, make sure they don’t both fire conflicting actions (e.g., two competing tasks). One “Prospect replied” workflow listening for either signal is usually cleaner.