The Workflow Library

Library / Reporting and alerts / reporting-alerts-031

Quarter-end pipeline snapshot property set (amount and stage captured on a fixed date)

Reporting and alertsDealData Hub ProfessionalAdvanced~50 min to buildFull spec

Outcome. On a fixed schedule at the end of each quarter, every open deal gets its amount and stage frozen into snapshot properties, so quarter-over-quarter pipeline comparisons do not get overwritten by later edits to the live fields.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-031
flowchart TD
    A[Scheduled trigger: quarter end, 18:00] --> B[Enrollment: open deals across pipelines]
    B --> C[Set snapshot_amount_q_end = current amount]
    C --> D[Set snapshot_stage_q_end = current stage]
    D --> E[Set snapshot_date = today]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when finance or RevOps needs a point-in-time pipeline value that survives later amount or stage changes on the same deal.
  • UseUse it to build a trend report of pipeline composition across quarters without exporting a manual snapshot each time.
  • SkipDo not use it if the portal already exports pipeline snapshots through a data warehouse or BI tool on a schedule. That is a cleaner source of truth than CRM properties for historical trend analysis.
  • SkipDo not use it on a portal with only one pipeline stage in active use. A quarter-end freeze adds little when the field barely changes.
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.4 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 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.