The Workflow Library

Library / Reporting and alerts / reporting-alerts-046

Company rollup property: date of most recent deal stage change

Reporting and alertsCompanySales Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. Every company record shows the date its associated deals most recently changed stage, so account managers can see pipeline momentum, or the lack of it, without opening every associated deal.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-046
flowchart TD
    A[Deal stage changes] --> B[Set last_stage_change_date = now, on the deal]
    B --> C[Company rollup recalculates automatically]
    C --> D[most_recent_deal_stage_change_date reflects the latest across all associated deals]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it to flag accounts whose deals have gone quiet, no stage movement in a while, as candidates for a manual check-in.
  • UseUse it alongside reporting-alerts-021 and reporting-alerts-022 for a fuller account-level pipeline visibility set: open count, total value, and now recency of movement.
  • SkipDo not use it if deals move through stages very frequently as a side effect of automation rather than genuine progress; in that case this date reflects automation noise, not real momentum.
  • SkipDo not use it as a substitute for reviewing deal-level stage history when the actual sequence of stage changes matters, not just the most recent one.
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.3 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.