The Workflow Library

Library / Reporting and alerts / reporting-alerts-035

Audit property: record owner change log (who owns what, when it changed)

Reporting and alertsDealData Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. Every time a deal's owner changes, a timeline note records who it changed from and to, and a timestamp property tracks when, so ownership history stays visible without opening property history for every deal.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-035
flowchart TD
    A[Deal owner changes] --> B[Create note: owner changed from previous_owner_snapshot to current owner]
    B --> C[Set last_owner_change_date = now]
    C --> D[Set previous_owner_snapshot = current owner, for next time]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it on a portal where deal ownership changes matter for accountability, for example after a rep leaves, a round-robin reassignment, or a manager reallocation.
  • UseUse it when the team needs a readable "changed from X to Y" trail on the record itself, not only the native property history panel.
  • SkipDo not use it on a portal with high-frequency automated owner reassignment (for example a rotation workflow firing many times a day). It will flood the timeline with notes; see Known pitfalls for a throttling approach.
  • SkipDo not treat this as a substitute for HubSpot's own property history, which already logs every owner change with the user who made it; this fiche adds a readable note, it does not replace that audit trail.
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.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.