Outcome. A manager gets a recurring nudge to check rep workload instead of finding out a rep is overloaded three weeks later during a pipeline review.
Workflow map
Enrollment, branches and actions at a glance
lead-routing-034
flowchart TD
A[Scheduled workflow: each weekday morning] --> B[Create review task for manager]
B --> C[Send report-link email to manager]
C --> D[Manager reviews Open leads by owner report]
D --> E{Any rep at or above threshold?}
E -->|Yes| F[Remove rep from rotation pool or reassign leads manually]
E -->|No| G[No action, resume tomorrow]
When to use it, when not to
- UseUse it when the team has an agreed maximum number of open, unworked leads a rep should carry at once, and no one currently watches that number on a regular cadence.
- UseUse it as a review prompt, not a hard, automated block. HubSpot has no custom properties on users, so "rep capacity" cannot live as a field on the rep; it has to be measured by counting contacts, which is what the report below does.
- SkipDo not use it expecting an automatic real-time stop on assignment. See lead-routing-025 for the same limitation applied to daily lead volume; this fiche is the general capacity version of that same pattern.
- SkipDo not use it if the team is small enough that a manager already reviews the pipeline daily; the extra reminder may be redundant.
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.2 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.
