Outcome. Each product a customer subscribes to has its own Subscriptions record with an end date that stays synced to whatever renewal deal covers it, so an account with several products no longer depends on a single company-level date that can only describe one contract at a time.
Workflow map
Enrollment, branches and actions at a glance
renewal-expansion-041
flowchart TD
A[Renewal deal reaches Closed Won] --> B[Custom code: find associated Subscriptions record]
B --> C{Exactly one match?}
C -->|Yes| D[Set Subscription End Date and Status = Renewed]
C -->|No| E[Return error, leave fields untouched]
D --> F[Done]
E --> G[Notify deal owner: sync failed]
When to use it, when not to
- UseUse it once accounts routinely carry more than one active
subscription with different values or terms, and renewal-expansion-001's
single company-level
Contract End Dateis no longer enough to represent them. - UseUse it as the structural upgrade from renewal-expansion-026's line-item bundle approach, for portals that need a standalone, associable record per subscription rather than line items bundled inside one deal.
- SkipDo not use it for accounts with a single simple subscription; renewal-expansion-001 is lighter to build and maintain for that case.
- SkipDo not use it without Sales Hub Enterprise (or another hub's Enterprise tier granting custom objects); custom objects are an Enterprise-tier capability and this fiche has no Professional-tier equivalent.
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.6 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, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
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.
