The Workflow Library

Library / Renewal and expansion / renewal-expansion-010

Cross-sell trigger from single-product account detection

Renewal and expansionCompanySales Hub ProfessionalIntermediate~35 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Sales Hub Professional, and one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written.

Outcome. An account owner gets a cross-sell task the moment an account settles into using only one product, instead of that account staying single-product for years by default.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-010
flowchart TD
    A[Company: Customer, Active Product Count = 1, no task yet] --> B[Set Cross-sell Task Created = true]
    B --> C[Add to Cross-sell Targets list]
    C --> D[Create task for owner]
    D --> E[Notify owner]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when the number of active products per account is already tracked in HubSpot, whether entered manually by CS or synced from billing.
  • UseUse it as a prompt for a conversation, not a guarantee the account wants or needs another product; the owner still qualifies the fit before pitching anything.
  • SkipDo not use it if product ownership only exists in a billing system with no sync into HubSpot. This workflow reacts to a property already on the company record; it does not calculate ownership itself.
  • SkipDo not re-run the same cross-sell task every time the workflow re-evaluates the account; the dedupe flag below is required, not optional.
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.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.