The Workflow Library

Library / Renewal and expansion / renewal-expansion-043

Co-term alignment workflow for multi-subsidiary renewal dates

Renewal and expansionCompanySales Hub EnterpriseAdvanced~65 min to buildFull spec

Outcome. When a parent account's contract end date changes, every subsidiary account under it gets its own contract end date aligned to match, so a multi-entity customer renews on one date instead of subsidiaries drifting onto separate cycles.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-043
flowchart TD
    A[Parent company Contract End Date changes] --> B[Custom code: find child companies]
    B --> C[Set each child's Contract End Date to match parent]
    C --> D{Any subsidiary update failed?}
    D -->|Yes| E[Notify parent owner: alignment incomplete]
    D -->|No| F[All subsidiaries synced]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it for customers structured as a parent company with several subsidiary company records, where the commercial agreement co-terms all subsidiaries to the parent's renewal date.
  • UseUse it once hierarchical (parent/child) company associations are already set up between the parent and each subsidiary; this workflow reacts to that structure, it does not create it.
  • SkipDo not use it for subsidiaries that intentionally keep independent contract terms; forcing alignment on an account that should stay separate creates incorrect renewal dates.
  • SkipDo not use it without Sales Hub Enterprise (or another hub's Enterprise tier); hierarchical company associations at the depth needed for a true parent/child structure, and the custom code this fiche relies on, both assume Enterprise-level account structure. (check in your portal: confirm the parent and child company association is readable in a workflow branch at this portal's tier, since HubSpot documents the hierarchy field itself but not its workflow branch conditions; the custom code half of this fiche separately needs Data Hub Professional or Enterprise (https://knowledge.hubspot.com/workflows/choose-your-workflow-actions))
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, 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.