Route leads by postal code / zip using a lookup table (postal-to-territory)

Outcome. A lead's postal code decides its territory automatically, without a rep or manager manually re-checking country or state fields.

Workflow map Enrollment, branches and actions at a glance lead-routing-033

flowchart TD
    A[Form submitted with postal code] --> B[Hidden field maps postal code to Territory client-side]
    B --> C[Territory set on contact]
    C --> D[lead-routing-001 enrolls and rotates]
    E[Daily scheduled check] --> F{Territory unknown, postal code known?}
    F -->|Yes| G[Add to Needs postal-to-territory mapping list]
    G --> H[Sales ops updates mapping, bulk-imports Territory]
    H --> D
    F -->|No| E

When to use it, when not to

• UseUse 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).
• UseUse 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.
• SkipDo not use it if territories already line up cleanly with country or state; branch directly on those default properties instead, see lead-routing-006.
• SkipDo 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.