The Workflow Library

Library / Reporting and alerts / reporting-alerts-027

Counter property: number of times a deal has changed pipeline stage

Reporting and alertsDealData Hub ProfessionalAdvanced~60 min to buildFull spec

Outcome. Every deal carries a running count of how many times it has changed pipeline stage, so reporting can flag deals bouncing back and forth instead of moving steadily forward.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-027
flowchart TD
    A[Deal stage changes] --> B[Increment deal_stage_change_count by 1]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it to surface deals that keep moving backward and forward between stages, a sign of an unclear process, a stuck negotiation, or bad data hygiene, rather than progressing.
  • UseUse it as an input to a deal-health score alongside time-in-stage and days-since-last-activity properties.
  • SkipDo not use it if the goal is simply how long a deal has been in its current stage. That is a duration question this counter does not answer. Pair with the stage-entry timestamp properties from reporting-alerts-002 for that.
  • SkipDo not use it on a portal with several pipelines with very different stage counts without deciding first whether the counter should reset when a deal is moved between pipelines, see Known pitfalls.
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.2 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.2 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 reporting and alerts 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.