Create or update a territory custom object record when an account is assigned to a territory
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.
OutcomeEvery distinct territory value used on companies gets exactly one Territories record with a running account count, instead of sales ops keeping a separate spreadsheet of who owns which patch.
Workflow mapsales-ops-022
When to use it, when not to
Use it
- Use it when territory reporting needs to live on a record you can associate other objects to (deals, contacts, tasks) rather than staying stuck as a text or enumeration value on the company alone.
- Use it once your
Territoryvalues are stable and standardized (a fixed list, not free text) so one company value maps to exactly one territory record.
Read more on when to use itShow less
Skip it
- Do not use it if your territory model changes shape often (frequent re-splits, renames); every rename means a new territory record accumulates unless you actively archive the old one, since this workflow only creates or increments, it never merges or renames existing records.
- Do not build this if you only need territory reporting inside a dashboard filter on the company property itself; a dedicated custom object is worth it mainly when you need to associate other records (like a territory owner's tasks or plan documents) to the territory itself.
Read more on when to skip itShow less
The rest of this spec
Not the workflow you needed?
More in Sales ops
50 specs in this section
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.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Read the free Sales ops spec