Outcome. A new lead is routed to the rep who specializes in the channel that brought them in, so a paid-search lead and an organic-referral lead do not land with the same generalist.
Workflow map
Enrollment, branches and actions at a glance
lead-routing-020
flowchart TD
A[Contact created] --> B{Original Source?}
B -->|Paid Search| C[Rotate to Paid Search reps]
B -->|Paid Social| D[Rotate to Paid Social reps]
B -->|Organic/Direct/Referral| E[Rotate to General SDR pool]
B -->|Email Marketing| E
B -->|blank / offline / unmapped| F[Notify sales ops + add to Needs manual routing list]
C --> G[Set routed date, notify, create call task]
D --> G
E --> G

When to use it, when not to
- UseUse it when reps specialize by acquisition channel (paid search, paid social, organic, email) rather than by territory or product.
- UseUse it when the standard
Original SourceandOriginal Source Drill-Down 1properties are populated reliably by HubSpot tracking on every relevant page. - SkipDo not use it if channel and territory both need to drive routing; pick one as the primary key and use the other as a secondary filter or a nested branch, do not build two separate, unrelated rotation workflows for the same new lead.
- SkipDo not use it if most traffic arrives through non-HubSpot-tracked
forms; those contacts will show
Original Sourceas "Offline Sources" and will not branch usefully.
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.15 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.





