Outcome. A deal cannot move out of Closed Won back into an open stage until a named approver signs off, so a won deal that already triggered invoicing or provisioning does not get quietly reopened and re-closed without anyone downstream knowing.
Workflow map
Enrollment, branches and actions at a glance
deal-hygiene-048
flowchart TD
A[Deal marked Closed Won, Reopen Approved checked] --> B{Reopen Reason provided?}
B -->|no| C[Notify owner, need a reason, exit]
B -->|yes| D[Notify Reopen Approver]
D --> E[Create approval task]
E --> F[Delay 1 business day]
F --> G{Still pending after delay?}
G -->|yes| H[Escalation notification]
G -->|no| I[Exit, resolved]
When to use it, when not to
- UseUse it once deal-hygiene-030's Closed Won finance notification is already live, this fiche protects the integrity of that trigger, an unapproved reopen risks a second, unintended invoicing event or a confusing finance record.
- UseUse it together with the native required-property-per-stage setting, exactly like deal-hygiene-015 and deal-hygiene-028, the workflow manages notification and review, the required-property setting is what actually blocks the move.
- SkipDo not use it if reopening a Closed Won deal is a routine, expected action on your team, for example correcting a data-entry mistake made minutes after closing, in that case a lighter-weight confirmation step is more appropriate than a full approval gate.
- SkipDo not use it on Sales Hub Professional expecting the same enforcement, the required-property setting itself works on Professional, but this fiche's Enterprise designation assumes the same field-level-permission protection used in deal-hygiene-015, restricting who can set the approval property in the first place. Permission sets require an Enterprise subscription on Marketing, Sales, Service, Data, Content or Revenue Hub (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.4 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.8 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 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 deal hygiene 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.
