The Workflow Library

Library / Lead nurturing / lead-nurturing-037

Video engagement based nurture (percentage watched)

Lead nurturingContactMarketing Hub ProfessionalAdvanced~45 min to buildFull spec

Outcome. A contact who watches a gated or embedded video gets a follow-up email matched to how much of it they actually watched, instead of every viewer getting the same generic next step.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-037
flowchart TD
    A[video_watch_percentage set, branch not sent] --> B{>= 75 percent?}
    B -- Yes --> C[Send: ready for a demo]
    B -- No --> D{>= 25 percent?}
    D -- Yes --> E[Send: more on what you watched]
    D -- No --> F[Send: quick recap]
    C --> G[Set video_nurture_branch_sent = true]
    E --> G
    F --> G
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse when a video hosting platform (for example Wistia or Vidyard) is already connected to HubSpot and writes watch data back to the contact record.
  • UseUse for a specific high-value video (a product demo, an explainer) where watch depth is a meaningful signal of intent.
  • SkipDo not use this if the account has no video platform integration; HubSpot does not natively track percentage watched for embedded third-party video without one, and building that tracking from scratch is out of scope for a workflow-only build.
  • SkipDo not use this for short videos under a minute, where watch percentage is a weak signal (most people finish short videos regardless of interest).
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.6 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the lead nurturing pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.