The Workflow Library

Library / Deal hygiene / deal-hygiene-019

Deal missing line items before close

Deal hygieneDealSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A deal heading into a late stage with no line items gets caught, so the deal amount and the actual products sold line up before the deal closes.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-019
flowchart TD
    A[Deal enters late stage] --> B{Has an associated line item?}
    B -->|yes| C[Set Has Line Items = true, exit]
    B -->|no| D[Create task for owner]
    D --> E[Notify owner]
    E --> F[Delay 2 business days]
    F --> G{Line item added now?}
    G -->|yes| H[Set Has Line Items = true, exit]
    G -->|no| I[Reminder notification]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when deals commonly reach late stages with an Amount typed in manually but no actual line items backing it up, which breaks reporting on products sold.
  • UseUse it together with a native required-property-per-stage setting if you want a hard stop, this workflow only detects and nudges.
  • SkipDo not use it if your team does not use the Products / line items feature at all and just tracks a flat Amount. This fiche assumes line items are the expected source of the deal amount.
  • SkipDo not use it on pipelines where a deal can legitimately close without line items, for instance services scoped outside of Products.
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.3 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.8 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 deal hygiene 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.