Route leads by postal code / zip using a lookup table (postal-to-territory)
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: Sales Hub Professional.
Per-hub plans: also Marketing Hub Professional
On per-hub plans, one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written. On seat pricing the edition covers both.
When to use it, when not to
Use it
- Use it when territories are drawn at a finer level than country or state (specific zip or postal code ranges split between reps in the same city or region).
- Use it as the enrichment step that feeds lead-routing-001, not as a
replacement for it: this fiche's job is to fill
Territory, lead-routing-001's job is to rotate once it is filled.
Read more on when to use itShow less
Skip it
- Do not use it if territories already line up cleanly with country or state; branch directly on those default properties instead, see lead-routing-006.
- Do not expect a live, native postal-code lookup inside a single workflow step. HubSpot workflows do not have a built-in "look up this value in a table" action; this fiche uses a pre-built mapping applied before or at lead creation, not a real-time calculation, see Known pitfalls.
Read more on when to skip itShow less
The rest of this spec
Not the workflow you needed?
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 Lead routing spec