The Workflow Library

Library / Lead nurturing / lead-nurturing-036

Sunset / final-attempt re-engagement before suppression

Lead nurturingContactMarketing Hub ProfessionalSimple~25 min to buildFull spec

Outcome. Long-inactive contacts get one clear final email before being moved off active marketing sending, protecting deliverability without silently ghosting people who might still want to hear from the company.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-036
flowchart TD
    A[On cold list, 180+ days inactive] --> B[Send: still want to hear from us]
    B --> C[Delay 7 days]
    C --> D{Opened or clicked?}
    D -- Yes --> E[Remove from cold list]
    D -- No --> F[Set non-marketing contact]
    F --> G[Add to Sunset - do not email list]
    E --> H[Set sunset_nurture_completed = true]
    G --> H
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse on contacts with no email open or click for a long stretch (180 days is a common baseline) to clean the actively-sent list before it drags down deliverability.
  • UseUse as the last step of a re-engagement effort, after lead-nurturing-005 has already tried to win the contact back with real content.
  • SkipDo not use this on contacts who are dormant only because they are customers on a low-touch account (check lifecycle stage or a customer flag first); route those through a different cadence instead of suppression.
  • SkipDo not run this without stakeholder sign-off on the suppression list name and process, since it changes who receives future campaigns.
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.