Skip to content
The Workflow Library
Get the full library

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

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Deal2 stepsUpdated for HubSpot seat pricing
OutcomeEvery 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 mapreporting-alerts-027
Deal stage changes leads to Increment deal_stage_change_count by 1. Deal stage changes Increment deal_stage_change_count by 1
Deal stage changes leads to Increment deal_stage_change_count by 1. Deal stage changes Increment deal_stage_change_count by 1

When to use it, when not to

Use it

  • Use 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.
  • Use it as an input to a deal-health score alongside time-in-stage and days-since-last-activity properties.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 2 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 2 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 1 case, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Reporting and alerts spec

Not the workflow you needed?

More in Reporting and alerts

50 specs in this section

See all 50 This category, 39 EUR
FreeSlack alert: deal marked Closed Won (revenue milestone notification)Deal4 steps Stage-entry timestamp properties for pipeline velocity reportingDeal5 steps Counter property: number of times a support ticket has been escalatedTicket2 steps Timeline note logging on critical property change (audit visibility)Deal2 steps

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library