Skip to content

Notify AE and create a handoff task when a territory custom object record changes owner

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

Enterprise

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

Custom3 stepsUpdated for HubSpot seat pricing
OutcomeWhen a territory is reassigned to a new AE, that AE gets notified and a handoff task the same day, instead of finding out weeks later when a customer calls in confused about who owns their account.
Workflow mapsales-ops-042
Territory record owner changes leads to Set Territory previous owner id. Set Territory previous owner id leads to Notify new owner of the reassignment. Notify new owner of the reassignment leads to Create handoff review task for new owner. Territory record owner changes Set Territory previous owner id Notify new owner of the reassignment Create handoff review task for new owner
Territory record owner changes leads to Set Territory previous owner id. Set Territory previous owner id leads to Notify new owner of the reassignment. Notify new owner of the reassignment leads to Create handoff review task for new owner. Territory record owner changes Set Territory previous owner id Notify new owner of the reassignment Create handoff review task for new owner

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

When to use it, when not to

Use it

  • Use it together with sales-ops-022 (create or update a territory custom object record), once Territories records exist and are actively owned by individual AEs.
  • Use it whenever territory ownership changes for any reason: reorg, headcount change, or a manual reassignment by sales ops.
Read more on when to use itShow less

Skip it

  • Do not use it if territory ownership is tracked only at the company level rather than on a dedicated Territories object; adapt this pattern to a company-based trigger instead in that case.
  • Do not use it if territory reassignments are rare and always accompanied by a manual handoff meeting already; the value here is catching reassignments that would otherwise slip through without a nudge.
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 · 3 numbered actions

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

Known pitfalls · 5

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 lists the fields to create. The workflow JSON documents the build.

Install · By hand

This workflow runs on a custom object that only exists in your portal. Build it from the spec; the one-click installer does not cover it.

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 Sales ops spec

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