Outcome. When a rep leaves the team, their open leads land back with an active rep through the normal rotation instead of piling up on one manager who happened to catch them at deactivation time.
Workflow map
Enrollment, branches and actions at a glance
lead-routing-012
flowchart TD
A[Rep deactivated, records bulk-reassigned to placeholder owner] --> B[This workflow enrolls]
B --> C[Rotate to active rep pool]
C --> D[Set routed date + reassigned flag]
D --> E[Notify new owner]
E --> F[Add to Redistributed audit list]
When to use it, when not to
- UseUse it right after a rep is deactivated in HubSpot, to spread their still-open leads evenly across the remaining active team instead of dumping them all on a single holder.
- UseUse it as a companion to the native HubSpot user deactivation flow, not a replacement for it. Deactivating a user in Settings > Users already lets an admin choose what happens to that user's owned records; this workflow re-distributes the ones sent to a shared holding account.
- SkipDo not use it as your only reassignment mechanism for departures. If your admin process reassigns each departing rep's records directly to a specific named successor at deactivation time, this workflow has nothing to do and should stay off.
- SkipDo not use it for records with a required specific owner (named accounts). Exclude those first, see lead-routing-011.
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.5 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.5 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 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.
