Outcome. A renewal deal cannot stay in Closed Won without a signed contract link attached, so finance and legal are not left chasing paperwork after a deal is already counted as booked revenue.
Workflow map
Enrollment, branches and actions at a glance
renewal-expansion-048
flowchart TD
A[Deal Stage becomes Closed Won, Deal Type = Renewal, Signed Contract Link unknown] --> B[Set Deal Stage = On Hold - Missing Contract]
B --> C[Set Closed Won Reverted = true]
C --> D[Create task: add contract link]
D --> E[Notify owner: reverted]
When to use it, when not to
- UseUse it once your pipeline stages support required properties, and the goal is to make a signed contract link mandatory before a renewal counts as closed.
- UseUse it as a two-part control: the actual blocking happens through HubSpot's native required-stage-properties setting on the pipeline itself, not through a workflow. This fiche's workflow is a safety net that catches and corrects the cases where a deal still slipped through, since workflows react after a change happens, they do not prevent a manual stage move in the moment the way a stage requirement does.
- SkipDo not use it expecting the workflow half alone to stop a rep from moving a deal to Closed Won; build the native required-property setting on the Closed Won stage first, and treat the workflow as the backstop, not the primary control.
- SkipDo not use it on pipelines where a signed contract link genuinely is not the norm (a self-serve, no-contract renewal flow, for example); forcing the property on those deals adds friction without matching how the business actually operates.
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.5 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.4 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 renewal and expansion 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.
