The Workflow Library

Library / Renewal and expansion / renewal-expansion-012

Renewal deal amount pre-populated from current subscription value

Renewal and expansionDealSales Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. A new renewal deal opens with a realistic amount already filled in, taken from what the account is actually paying today, instead of a blank field someone has to look up manually.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-012
flowchart TD
    A[Deal Type = Renewal, Amount unknown, not yet pre-filled] --> B[Copy Current Subscription Value to deal Amount]
    B --> C[Set Deal Amount Pre-filled = true]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it whenever renewal deals are created without an amount, and the current subscription value is already tracked in HubSpot from billing, an integration, or manual CS entry.
  • UseUse it as a companion to renewal-expansion-001, which creates the renewal deal itself; this fiche is the amount-filling step for portals that did not build that into the creation workflow directly.
  • SkipDo not use it if subscription value only lives in a billing or finance system with no sync into HubSpot. HubSpot has no native subscription or contract object; this workflow reacts to a plain number property that something else has to keep current.
  • SkipDo not treat the pre-filled amount as final. It reflects the current subscription only; price increases, added seats, or downgrades still need a person to adjust the deal before it closes.
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.2 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 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.