The Workflow Library

Library / Lead nurturing / lead-nurturing-049

Reactivation nurture triggered by repeat website visit after silence

Lead nurturingContactMarketing Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A contact who has gone quiet for a long stretch and then comes back to the site gets a timely "welcome back" nurture instead of being treated as still dormant until a separate campaign happens to reach them.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-049
flowchart TD
    A[Page view, dormant_contact = true] --> B[Set dormant_contact = false]
    B --> C[Send: welcome back]
    C --> D[Delay 3 days]
    D --> E[Send: related content]
    E --> F[Set reactivation_nurture_completed = true]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse for contacts already flagged as dormant (no engagement for an extended period) who then show a fresh sign of interest by visiting the site again.
  • UseUse when the account tracks page views reliably and can flag dormancy with a companion process (a scheduled workflow, or the pattern in lead-nurturing-005).
  • SkipDo not use this for contacts who are actively engaged already; the enrollment filter below specifically requires the dormant flag, so an active contact visiting the site again is expected behavior, not a reactivation event.
  • SkipDo not treat a single page view as strong enough signal on its own to trigger a sales handoff; this fiche nurtures first and lets a later click or a specific high-intent page (see lead-nurturing-012) escalate to sales.
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.5 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.