Walnut + HubSpot: High-Impact Use Cases
Overview
Demo engagement data from Walnut will appear in HubSpot as long as your HubSpot Integration is set up, whether you’ve added a lead form or not.
Once HubSpot is connected, Walnut enriches your records with both demo details and engagement behavior so your team can follow up with context, not guesswork.
Why this matters:
Walnut turns HubSpot into a behavior-driven system—helping your team prioritize faster, personalize outreach, and automate smarter using real product engagement.
Session Identification & Sync Timing
Walnut only enriches CRM records when a session can be tied to a known person. In other words, email identification is what turns a demo view into CRM-ready engagement data.
Walnut supports multiple identification methods including:
- HubSpot lead forms
- Walnut email gates
- URL parameters
Identified vs Anonymous:
Identified session: Activity is tied to a contact and synced to HubSpot.
Anonymous session: Activity is tracked but not tied to a record until identification occurs.
Session-Level Data
- Session ID
- Session timing (start, end, duration)
- Completion rate
- Viewed screens and guides
- CTA clicks
- Demo metadata
Tip:
Use session-level data to understand exactly what happened during a visit—not just that it happened.
Sync Timing
- Form submissions appear quickly
- Engagement data may take up to a few hours
- Sync begins after inactivity (~30 minutes)
Best practice:
Expect the most complete data after the session has ended.
Where to Find Walnut Data in HubSpot
- Activities timeline: Session-level engagement
- Contact properties: Aggregated demo data
Together, these provide both a summary view and a detailed interaction history.
Walnut Properties in HubSpot
- Average completion rate
- Total time spent
- Latest demo viewed
- Total demo views
- List of demos seen
Quick read tip:
Start with last demo viewed, completion rate, and time spent.
Walnut + HubSpot: High-Impact Use Cases
Walnut demo and playlist engagement data turns HubSpot into a more actionable system for follow-up, segmentation, automation, personalization, and reporting. Instead of guessing what a prospect or customer cares about, your team can use actual product engagement signals to decide what to send next, who to prioritize, and how to personalize outreach.
Key takeaway:
Walnut data in HubSpot helps teams move from static lead records to behavior-based action. That means better prioritization, more relevant follow-up, and stronger automation across marketing, sales, onboarding, and customer education.
1. Capture and Identify Leads with HubSpot Forms Inside Walnut
One of the most common use cases is embedding a HubSpot lead form directly inside a Walnut demo or playlist. This allows teams to identify viewers without sending them away from the experience.
Once the form is submitted, HubSpot creates or updates the contact record, and Walnut can begin syncing identified session and engagement data into that record.
This is especially useful when you want to:
- Capture high-intent inbound traffic directly inside a demo
- Identify anonymous viewers before unlocking deeper content
- Pass known contacts into HubSpot with richer engagement context
Example:
A marketing team embeds a HubSpot form after the first few screens of a guided demo. Once the viewer submits the form, the contact is created in HubSpot and enriched with the demo name, completion rate, session length, and viewed screens.
2. Personalize Sales Follow-Up with Actual Demo Engagement
Once Walnut data appears in HubSpot, reps can personalize outreach based on what the contact actually viewed instead of relying on generic follow-up.
Fields like Walnut last demo name view, latest completion rate, CTA clicked, viewed screens, and session-level timeline activity give reps a fast read on interest and intent.
This helps teams:
- Reference the exact demo or workflow the prospect explored
- Focus follow-up on the features that drove engagement
- Prioritize higher-intent contacts more quickly
Example:
A rep sees that a prospect viewed the “Reporting Overview” demo, reached an 82% completion rate, and clicked a CTA tied to integrations. Instead of sending a general follow-up, the rep sends a tailored email focused on reporting and integration workflows.
3. Trigger HubSpot Workflows Using Walnut Engagement Data
Walnut properties can be used inside HubSpot workflows to automate next steps based on demo behavior.
Because Walnut writes engagement data back to HubSpot properties and timeline events, teams can build workflows around real product interaction, not just form fills.
Common workflow examples include:
- Trigger a sales task when a contact reaches a high completion rate
- Send a follow-up email when a prospect views a specific demo
- Assign leads to a rep when total demo views exceeds a threshold
- Nudge contacts who submitted a form but never completed the demo
Example:
A HubSpot workflow checks whether Walnut latest demo completion rate is greater than 70% and whether Walnut total demo views is at least 2. If both are true, HubSpot automatically creates a follow-up task for sales and adds the contact to a high-intent sequence.
Best practice:
Start simple. Build your first workflow around one or two high-signal properties like last demo viewed, latest completion rate, or total demo views.
4. Send HubSpot Email Campaigns with Walnut URL Parameters at Scale
HubSpot is also a strong distribution layer for Walnut experiences. Teams can send demo and playlist links through HubSpot emails and use URL parameters to personalize the experience, track attribution, and identify viewers more cleanly.
This is especially powerful for one-to-many sends, nurture flows, webinar follow-ups, and outbound campaigns where you want the same demo to feel personalized without manually editing it.
Common ways teams use this include:
- Appending email address parameters for cleaner identification
- Passing campaign values like source, persona, segment, or event name
- Personalizing demo content based on HubSpot token values
- Tracking which email campaign drove the engagement
This makes it easier to:
- Scale personalized demo distribution across large audiences
- Track which campaigns or sequences are driving product engagement
- Keep one demo or playlist reusable across many audiences
Example:
A marketing team sends a HubSpot email campaign promoting a product walkthrough playlist. The email link includes parameters like email={{contact.email}}, campaign=product_launch_q2, and persona=marketing_ops. When recipients open the demo, Walnut can identify the session more reliably, personalize the experience, and pass the engagement back into HubSpot with campaign context attached.
5. Build Behavior-Based Segments in HubSpot
Walnut properties can also be used to build active lists and segments inside HubSpot.
This allows teams to group contacts based on how they engaged with demos, not just how they entered the database.
Useful segment examples:
- Contacts who viewed a specific demo in the last 7 days
- Contacts with high completion but no meeting booked
- Contacts with multiple demo views across sessions
- Contacts who clicked a CTA inside a Walnut experience
Example:
A team creates an active HubSpot list for contacts whose Walnut total demo views is greater than 1 and whose Walnut last demo view occurred in the last 14 days. That list is then used for targeted follow-up and retargeting.
6. Improve Campaign and Content Performance
HubSpot and Walnut together give marketing teams a better view of how demo content performs after distribution.
Instead of stopping at opens and clicks, teams can look at what happened inside the experience itself.
This can help answer questions like:
- Which campaigns drove the most engaged demo sessions?
- Which demos had the strongest completion rates?
- Which experiences created CTA clicks or repeat visits?
- Which content is worth reusing, expanding, or repositioning?
Example:
Two HubSpot nurture emails each send viewers to a different Walnut demo. By comparing downstream engagement inside Walnut, the team sees that one experience drives much longer session time and stronger CTA activity, and uses that insight to refine the campaign.
7. Power Pre-Sales & Demo Strategy
Use historical demo engagement to guide live demos and sales conversations.
- See what a prospect already explored before a call
- Skip basics and focus on high-interest areas
- Tailor demo flow to match prior engagement
This creates more efficient, high-signal conversations and reduces redundant walkthroughs.
Example:
Before a live demo, a rep checks the contact’s HubSpot record and sees they already engaged deeply with reporting and dashboards. The rep starts there instead of repeating a general walkthrough.
8. Enable Product-Led Follow-Up & Education
Combine Walnut data with HubSpot workflows to guide prospects and customers through ongoing learning.
- Send next-step playlists based on engagement
- Trigger onboarding content after specific demos are viewed
- Nudge users who didn’t complete key flows
This creates a continuous, product-led journey beyond the initial demo.
Example:
A contact finishes an introductory product demo but does not engage with advanced workflows. HubSpot automatically sends a follow-up playlist with deeper feature education and practical next steps.
9. Measure Impact & ROI
Use Walnut engagement data to connect product interaction to pipeline and revenue outcomes.
- Compare engagement across won vs lost deals
- Identify which demos influence conversion
- Track how engagement correlates with deal velocity
Pro Tip:
Start simple: track last demo viewed, completion rate, and time spent against pipeline stages. These three signals alone can reveal strong intent patterns.
HubSpot Workflow Playbook: High-Impact Automations
Below are practical workflow patterns you can build in HubSpot using Walnut data. These are designed to be quick to implement and high impact.
Tip:
Start with 1–2 workflows and expand. Even simple automations can dramatically improve speed-to-follow-up.
Workflow 1: High-Intent Lead Alert 🚨
Trigger: Walnut latest demo completion rate > 70%
- Create task for sales rep
- Send Slack or email notification
- Assign lifecycle stage = MQL or SQL
Outcome: Sales engages at peak interest.
Workflow 2: Demo Follow-Up Sequence
Trigger: Walnut total demo views > 0
- Send follow-up email with a related playlist
- Wait 2–3 days
- Send deeper-dive demo or case study
Outcome: Converts passive viewers into active conversations.
Workflow 3: Re-Engagement Nudge
Trigger: Demo viewed but completion rate < 30%
- Send simplified or guided demo
- Include short “start here” messaging
- Offer quick walkthrough or call option
Outcome: Recaptures dropped engagement.
Workflow 4: Feature Interest Routing
Trigger: Last demo viewed = specific product area
- Assign to relevant sales specialist or SE
- Send targeted follow-up content
- Add to segmented list
Outcome: Aligns follow-up with actual product interest.
Workflow 5: Post-Event / Playlist Follow-Up
Trigger: Playlist engagement or multiple demo views
- Send recap playlist or hub
- Trigger SDR follow-up
- Track engagement progression over time
Outcome: Extends conversations beyond the event or meeting.
Workflow 6: Product-Led Onboarding Flow
Trigger: Demo viewed + form submitted
- Send onboarding playlist
- Trigger educational email series
- Introduce key workflows step-by-step
Outcome: Creates a guided onboarding journey without manual effort.
Best Practices
- Focus on high-signal properties first
- Use URL parameters for scalable personalization
- Combine Walnut data with lifecycle stages and campaign data
- Start simple, then layer complexity
🚀 Getting Started:
Start with one high-impact workflow like High-Intent Lead Alert, then layer in follow-ups, segmentation, and nurture sequences. As your dataset grows, your workflows become more precise—and more powerful.
