Outcome. A company sitting above an agreed number of simultaneously open deals, counted across every pipeline, gets flagged with the exact count, so sales ops can catch portfolio sprawl a single-pipeline view would never surface.
Workflow map
Enrollment, branches and actions at a glance
deal-hygiene-050
flowchart TD
A[Company has at least one associated deal] --> B[Custom code: count open deals across pipelines]
B --> C[Set Open Deal Count from code output]
C --> D{Cap exceeded, per code output?}
D -->|yes| E[Set Deal Count Cap Exceeded = true]
E --> F[Create review task for sales ops]
D -->|no| G[Set Deal Count Cap Exceeded = false]
When to use it, when not to
- UseUse it once a company can plausibly have open deals in more than one pipeline at the same time, for example a new-business pipeline and a separate expansion or renewal pipeline running in parallel.
- UseUse it as a portfolio-level hygiene check, not a hard cap enforced at deal creation, this fiche flags after the fact, it does not stop a new deal from being created.
- SkipDo not use it if your portal only has one pipeline, or if companies never realistically carry more than one or two open deals, the count this fiche computes will rarely be interesting.
- SkipDo not attempt this with native workflow branch conditions alone. Counting associated deals across every pipeline for a company and comparing the total to a cap is arithmetic and a cross-pipeline aggregation that plain workflow actions cannot do, this fiche's primary build path is a custom coded action, which requires Data Hub Professional or Enterprise in addition to the Sales Hub tier this pack's taxonomy declares (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.6 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 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.
