Skip to content
The Workflow Library
Get the full library

Audit visibility: internal note auto-logged on ticket priority change

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: Service Hub Professional.

Ticket3 stepsUpdated for HubSpot seat pricing
OutcomeEvery time a ticket's priority changes, a note logs automatically to the ticket's timeline with the new priority and a timestamp, giving support leads a visible trail without opening property history.
Workflow mapreporting-alerts-044
Ticket Priority changes leads to Create note on ticket timeline with new priority. Create note on ticket timeline with new priority leads to Set last_priority_change_logged_at = now. Ticket Priority changes Create note on ticket timeline with new priority Set last_priority_change_logged_at = now
Ticket Priority changes leads to Create note on ticket timeline with new priority. Create note on ticket timeline with new priority leads to Set last_priority_change_logged_at = now. Ticket Priority changes Create note on ticket timeline with new priority Set last_priority_change_logged_at = now

When to use it, when not to

Use it

  • Use it for lightweight, visible tracking of priority escalations and de-escalations on tickets that matter for SLA or leadership visibility.
  • Use it when support leads read ticket timelines directly and want inline change visibility rather than checking property history per ticket.
Read more on when to use itShow less

Skip it

  • Do not expect a true before/after log from this pattern alone. Native workflow tokens expose only the CURRENT, post-change value; for a "changed from X to Y" note, add the snapshot-property technique described in reporting-alerts-035.
  • Do not apply this to every ticket property. Priority is a high-signal field; logging every property change creates timeline noise nobody reads.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 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 · 3 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 · 3 cases, 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 Audit property: record owner change log (who owns what, when it changed)Deal4 steps Timeline note logging on critical property change (audit visibility)Deal2 steps Stage-entry timestamp properties for pipeline velocity reportingDeal5 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