The Workflow Library

Library / Lead routing / lead-routing-015

Route by lead score threshold to sales, below threshold to nurture

Lead routingContactMarketing Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A lead that clears the agreed score bar goes straight to a rep, while one that has not earned it yet drops into nurture instead of sitting untouched or getting a premature cold call.

Workflow map Enrollment, branches and actions at a glance lead-routing-015
flowchart TD
    A[HubSpot Score set / recalculated, owner unknown] --> B{Score >= threshold?}
    B -->|Yes| C[Rotate to SDR/AE pool]
    C --> D[Set routed date, notify owner, create call task]
    B -->|No| E[Set nurture track, add to list, enroll in nurture]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it as the gate between marketing automation and sales assignment when lead scoring is already configured and the team has agreed on a minimum score that means "ready for a human."
  • UseUse it to keep sales focused on genuinely warm leads while lower-score contacts keep getting nurtured until they earn the threshold.
  • SkipDo not use it if scoring is not yet configured or trusted; a bad threshold routes noise to sales and erodes trust in the whole system faster than no routing at all. Get scoring validated first.
  • SkipDo not use it for contacts who already have an owner from a prior sales-sourced touch; exclude those, an existing relationship should not be redirected into a generic nurture track because of a score recalculation.
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.6 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.8 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.