Outcome. A newsletter subscriber who shows real engagement over a month gets pulled into a proper conversion-focused nurture, while one who stays inactive gets flagged for a re-engagement pass instead of sitting in the newsletter list forever.
Workflow map
Enrollment, branches and actions at a glance
lead-nurturing-017
flowchart TD
A[Filter: newsletter subscriber, not yet evaluated] --> B[Set newsletter_engagement_count = 0]
B --> C[Delay 30 days]
C --> D{Engagement count >= 2?}
D -- Yes --> E[Set status = Graduated]
E --> F[Add to list: ready for nurture]
D -- No --> G[Set status = Needs Re-engagement]
G --> H[Add to list: low engagement]
When to use it, when not to
- UseUse when the newsletter is the widest, lowest-intent list in the database and needs a mechanical way to surface the subscribers worth a real nurture push.
- UseUse it as a feeder into another fiche, such as lead-nurturing-001 or 008, rather than building conversion content directly inside this workflow.
- SkipDo not use it if the newsletter send cadence is irregular. The 30-day evaluation window assumes at least three or four regular sends land in that period.
- SkipDo not use it as the only signal before a sales handoff. Newsletter engagement alone is a weak intent signal; combine with a stronger trigger like lead-nurturing-012 before creating any sales task.
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.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.
