The Workflow Library

Library / Lead nurturing / lead-nurturing-024

Multi-episode webinar series nurture

Lead nurturingContactMarketing Hub ProfessionalIntermediate~40 min to buildFull spec

Outcome. A registrant for episode one of a webinar series is automatically invited to episode two after attending, and to episode three after that, without a marketer manually rebuilding an invite list for each episode.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-024
flowchart TD
    A[Re-enrolls on attendance change] --> B{Attended Ep1, not Ep2?}
    B -- Yes --> C[Send: episode 2 invite]
    C --> D[Set next_invited = Episode 2]
    B -- No --> E{Attended Ep2, not Ep3?}
    D --> E
    E -- Yes --> F[Send: episode 3 invite]
    F --> G[Set next_invited = Episode 3]
    E -- No --> H{Attended Ep3?}
    G --> H
    H -- Yes --> I[Set next_invited = Series Complete]
    H -- No --> J[No action]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse for a genuine multi-part series where episode 2 assumes context from episode 1, and it makes sense to gate later invites on earlier attendance.
  • UseUse it once all episode dates are scheduled and each has its own registration page or form, before the series starts.
  • SkipDo not use it if the episodes are actually independent, standalone webinars that just happen to share a topic. Invite everyone to everything in that case, this fiche's gating logic is unnecessary overhead.
  • SkipDo not use it if only one or two episodes exist. Build lead-nurturing-004 (post-webinar follow-up) directly instead for a single-episode event.
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.9 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.