Outcome. A single "at risk" flag combines pipeline stage and inactivity into one signal, so a list or dashboard can surface deals worth a manager's attention without cross-referencing two separate reports.
Workflow map
Enrollment, branches and actions at a glance
deal-hygiene-022
flowchart TD
A[Deal in risk stage] --> B{Last Activity more than 10 days ago?}
B -->|no| C{Amount greater than 20000?}
C -->|yes| D[Flag = true, reason = stage-only]
C -->|no| E[Flag = false, reason = none]
B -->|yes| F{Amount greater than 20000?}
F -->|yes| G[Flag = true, reason = stage-and-inactivity]
F -->|no| H[Flag = true, reason = inactivity-only]
When to use it, when not to
- UseUse it once deal-hygiene-001 (inactivity alone) is already running and stage-only signals are not catching everything. This fiche layers stage and inactivity together.
- UseUse it as a triage flag for a weekly pipeline review, not as an automatic escalation. The combined condition is intentionally broader than either signal alone.
- SkipDo not use it if your pipeline stages are not a good proxy for risk, for example a pipeline where "negotiation" is a fast, healthy stage. The stage list needs to be agreed with sales leadership first.
- SkipDo not stack this on top of deal-hygiene-001 and deal-hygiene-006 without deciding which one owns the actual owner notification. Running three alerting workflows on the same deal creates redundant noise.
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.11 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.
