Outcome. A contact whose HubSpot Score drops below a previously-crossed threshold, meaning engagement has cooled off, gets one re-engagement email instead of quietly aging out of sight while the score keeps sliding.
Workflow map
Enrollment, branches and actions at a glance
lead-nurturing-026
flowchart TD
A[Re-enrolls on hubspotscore change, score < 50] --> B{Last sent unknown or 60+ days ago?}
B -- Yes --> C[Send re-engagement email]
C --> D[Set score_decay_flag = true]
D --> E[Set score_decay_last_sent = today]
B -- No --> F[No action, in cooldown]
When to use it, when not to
- UseUse once HubSpot Score is live and decay (score reduction from inactivity, if configured) or natural score decline from a lack of new positive actions is a normal part of the model.
- UseUse it as the mirror image of lead-nurturing-010: that fiche reacts to crossing a threshold upward, this one reacts to falling back below it.
- SkipDo not use it if the score model has no decay component and simply never goes down for an active contact; in that setup, a falling score is rare and this workflow will almost never fire, which is fine, but confirm that is actually expected before assuming the workflow is broken.
- SkipDo not treat a single dip in score as decisive. The cooldown property in Prerequisites exists to stop this from firing on every minor fluctuation.
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.
