Outcome. A single email send is followed by an event-based wait instead of a fixed delay, so a contact who opens moves to the next step right away, while a non-opener still gets routed to a fallback after 3 days, with no guessed delay length.
Workflow map
Enrollment, branches and actions at a glance
lead-nurturing-006
flowchart TD
A[Enrolled: list membership] --> B[Send: Nurture email A]
B --> C{Wait until opened, max 3 days}
C -- Opened in time --> D[Set outcome = Opened before timeout]
D --> E[Send: Nurture email B]
C -- Timed out --> F[Set outcome = No open within window]
F --> G[Send: alternate follow-up]
When to use it, when not to
- UseUse when the next action should depend on whether one specific email got opened, and speed matters for the engaged path. A flat 3-day delay would slow down someone who opens within minutes.
- UseUse this pattern as the building block other lead-nurturing fiches can drop in wherever they currently pair a fixed delay with an open check performed after the fact.
- SkipDo not use it to wait on an event that most contacts will never trigger without also giving the no-branch a real next step. The wait will time out for the majority of sends.
- SkipDo not stack two wait-until-event steps back to back on the same send without a clear reason. One wait per email keeps the workflow history readable.
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.7 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 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.
