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.
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]

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.
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.





