Outcome. A lead associated with a specific franchise location, branch office, or dealership is routed straight to that location's rep, instead of a central pool that has no notion of which local unit actually owns the relationship.
Workflow map
Enrollment, branches and actions at a glance
lead-routing-039
flowchart TD
A[Contact created / Franchise Location association set] --> B{Location associated?}
B -->|No| C[Add to Needs location match, notify ops]
B -->|Yes| D{Location record has an owner set?}
D -->|Yes| E[Copy owner from location to contact]
D -->|No| F[Add to Location missing rep assignment, notify ops]
E --> G[Set routed date, notify owner, create call task]
When to use it, when not to
- UseUse it when the business model has a franchise, dealer, branch, or multi-location structure represented in HubSpot as a custom object (for example a "Location" custom object), each with its own assigned rep or rep pool.
- UseUse it once the association between a lead and its location is captured reliably, either at intake (a location-selector form field) or through a downstream matching process (nearest location by postal code, for example).
- SkipDo not use it if locations are only tracked as a text property on the contact rather than a true custom object with its own records and associations; a simple property-based branch (lead-routing-006 style) is enough in that case and needs no custom object at all.
- SkipDo not use it without confirming custom objects are actually available on the portal; custom objects are a HubSpot Enterprise-tier feature across all hubs, not something addressable at Professional.
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.4 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.9 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 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 lead routing 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.
