The Workflow Library

Library / Lead nurturing / lead-nurturing-041

Disqualified-lead cooldown recycling nurture

Lead nurturingContactMarketing Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. Contacts marked disqualified by sales get a second look after a cooldown period, with a light re-introduction sequence instead of staying permanently marked off with no path back into the pipeline.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-041
flowchart TD
    A[Unqualified, disqualified 90+ days ago] --> B[Set hs_lead_status = Open]
    B --> C[Send: checking back in]
    C --> D[Delay 5 days]
    D --> E{Clicked check-in email?}
    E -- Yes --> F[Task: re-engaged, review]
    E -- No --> G[Send: one more resource]
    F --> H[Set disqualified_cooldown_completed = true]
    G --> H
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse when "disqualified" in the account's process usually means "not now" rather than "never" (budget timing, wrong stage, no current need), and circumstances can plausibly change.
  • UseUse with a fixed cooldown period long enough that revisiting makes sense (90 days is a reasonable default for most B2B cycles).
  • SkipDo not use this for disqualifications that mean genuinely never (wrong industry entirely, size mismatch that will not change, explicit request to not be contacted). Filter those out before enrollment, ideally with a disqualification reason property.
  • SkipDo not run this on a contact sales is actively re-engaging manually; check for a recent logged activity first.
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.