The Workflow Library

Library / Renewal and expansion / renewal-expansion-019

Next renewal date auto-set on renewal deal Closed Won

Renewal and expansionCompanySales Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. The moment a renewal deal closes won, the associated account's contract end date rolls forward to the next cycle and the renewal-creation flag resets, so the account is ready for the next renewal deal without anyone editing dates by hand.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-019
flowchart TD
    A[Deal closed won, Deal Type = Renewal] --> B{Contract Term Months known?}
    B -->|Yes| C[Set company Contract End Date = close date + term]
    C --> D[Reset Renewal Deal Created = false]
    B -->|No| E[Create task: confirm term]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it as the direct companion to renewal-expansion-001: that fiche creates the renewal deal from a contract end date, this one resets the date once the deal actually closes won.
  • UseUse it when contract terms are a fixed, known length (monthly, annual, multi-year) stored on the deal or known from the account's plan.
  • SkipDo not use it if contract length varies deal to deal in a way that is not captured anywhere; the term length used in step 2 below has to come from a real property, not a guess.
  • SkipDo not use it on new-business deals. It is scoped to Deal Type equal to Renewal, Closed Won.
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.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.