The Workflow Library

Library / Lead nurturing / lead-nurturing-023

Pre-event save-the-date and agenda teaser sequence

Lead nurturingContactMarketing Hub ProfessionalSimple~25 min to buildFull spec

Outcome. Contacts on an event invite list get a save-the-date, an agenda teaser, and a final reminder in the run-up to an event, and stop receiving the sequence the moment they actually register.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-023
flowchart TD
    A[Filter: on invite list, not registered] --> B[Send: save the date]
    B --> C[Delay until 14 days before event]
    C --> D{Registered yet?}
    D -- No --> E[Send: agenda teaser]
    D -- Yes --> F1[No action]
    E --> G[Delay until 3 days before deadline]
    G --> H{Registered yet?}
    H -- No --> I[Send: final reminder]
    H -- Yes --> F2[No action]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse for building pre-registration awareness on an invite list, before the person has registered for the event.
  • UseUse it upstream of lead-nurturing-003, which owns the confirmation and reminder sequence once someone has actually registered.
  • SkipDo not use it after registration opens and a contact has already signed up; check event_registration_confirmed before enrolling to avoid an awkward "save the date" landing after someone already booked their spot.
  • SkipDo not use it for an event with no fixed date far enough in advance to justify a save-the-date step; a single invite plus a registration reminder covers a short-notice event better.
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.12 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.