The Workflow Library

Library / Renewal and expansion / renewal-expansion-038

Expansion deal associated to original deal for pipeline lineage

Renewal and expansionDealSales Hub ProfessionalSimple~25 min to buildFull spec

Outcome. A new expansion deal is automatically linked back to the original deal that produced the account, so anyone opening either record can trace the full relationship history instead of piecing it together from memory.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-038
flowchart TD
    A[Deal Type = Expansion, Original Deal ID known, not yet linked] --> B[Create association to original deal]
    B --> C{Association succeeded?}
    C -->|Yes| D[Set Lineage Linked = true]
    C -->|No| E[Notify owner: check Original Deal ID]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it whenever expansion, upsell, or cross-sell deals are created for an existing account and the team wants a direct record-to-record link back to the deal that first won the account, not just a shared company association.
  • UseUse it as a companion to renewal-expansion-033, which is a common source of a first "original deal" reference on a newly converted account.
  • SkipDo not use it if your reporting only ever needs the shared company association; a direct deal-to-deal link is worth building specifically when lineage needs to survive company merges or when several deals exist per company and a shared company link alone is not specific enough.
  • SkipDo not use it if Original Deal ID is rarely populated in practice; an association workflow with mostly empty inputs adds workflow noise without much reporting value.
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.3 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.