Outcome. If any workflow, import, or person moves a contact's lifecycle stage backward, it gets corrected back to the highest stage the contact actually reached within minutes, with marketing ops notified, instead of silently distorting funnel reports.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-035
flowchart TD
A[Lifecycle stage changes] --> B{Rank vs highest_lifecycle_stage_reached}
B -->|Higher| C[Set highest_lifecycle_stage_reached = current stage]
B -->|Lower| D[Set lifecycle stage back to highest reached]
D --> E[Notify marketing ops of correction]
B -->|Equal| F[No action]
When to use it, when not to
- UseUse once lifecycle stage has regressed by accident (a stale import, a poorly scoped workflow, a manual mistake) and it has thrown off funnel or attribution reporting.
- UseUse as a safety net alongside good workflow hygiene, not instead of it.
- SkipDo not use if very few workflows write lifecycle stage and changes can be reviewed manually. The added complexity may not be worth it yet.
- SkipDo not expect this to prevent the downgrade from ever registering. HubSpot has no native way to block a property write before it happens in a standard workflow; this fiche detects the regression after the fact and corrects it. (check in your portal: check whether property validation rules can block the write outright on this account, since permission sets, which carry the edit restrictions, require Enterprise (https://knowledge.hubspot.com/user-management/create-permission-sets))
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 marketing ops 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.
