The Workflow Library

Library / Sales ops / sales-ops-042

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

Sales opsCustomSales Hub EnterpriseAdvanced~45 min to buildFull spec

Outcome. When 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 map Enrollment, branches and actions at a glance sales-ops-042
flowchart TD
    A[Territory record owner changes] --> B[Set Territory previous owner id]
    B --> C[Notify new owner of the reassignment]
    C --> D[Create handoff review task for new owner]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse 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.
  • UseUse it whenever territory ownership changes for any reason: reorg, headcount change, or a manual reassignment by sales ops.
  • SkipDo 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.
  • SkipDo 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.
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.2 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.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 sales ops 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.