Outcome. One nurture sequence, built once, sends content that reads as tailored to each contact's segment through personalization tokens and smart content, instead of maintaining a separate set of emails per segment.
Workflow map
Enrollment, branches and actions at a glance
lead-nurturing-038
flowchart TD
A[On audience list, segment known] --> B[Send: intro, smart content by segment]
B --> C[Delay 3 days]
C --> D[Send: proof point, smart content by segment]
D --> E[Delay 4 days]
E --> F[Send: CTA, smart content by segment]
F --> G[Set personalization_nurture_completed = true]
When to use it, when not to
- UseUse when segments differ mainly in wording and examples (company size, role, industry) rather than in the underlying offer or number of steps, since one shared email with tokens is cheaper to maintain than several full variants.
- UseUse when the account already has a reliable segment property set earlier in the funnel (a scoring or enrichment workflow, a form field).
- SkipDo not use this when segments need genuinely different content structure, different CTAs, or a different number of emails; use a branching pattern like lead-nurturing-008 instead.
- SkipDo not use personalization tokens for information the account is not confident is accurate; a wrong company size or industry guess in the email body reads worse than no personalization at all.
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.
