The Workflow Library

Library / Lead routing / lead-routing-008

Route by lifecycle stage change to MQL (assign to SDR queue)

Lead routingContactMarketing Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. The moment a contact becomes a Marketing Qualified Lead, an SDR is assigned automatically and gets a task to qualify the lead, instead of MQLs piling up in a shared list waiting for someone to notice.

Workflow map Enrollment, branches and actions at a glance lead-routing-008
flowchart TD
    A[Lifecycle stage becomes MQL, owner unknown] --> B[Rotate to SDR pool]
    B --> C[Set lead routed date]
    C --> D[Notify SDR by internal email]
    D --> E[Create qualification call task, due 1 business day]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when a lead-scoring or nurture workflow already sets Lifecycle stage to MQL, and a separate team of SDRs (not AEs) does first qualification.
  • UseUse it as the handoff point between marketing automation and the sales development team, distinct from lead-routing-002 which assigns on contact creation regardless of qualification.
  • SkipDo not use it if your org skips the MQL stage and hands leads straight from marketing to an AE. Use lead-routing-002 or lead-routing-015 instead.
  • SkipDo not use it for contacts who already have an owner from a prior sales-sourced touch. Exclude those so a marketing-driven MQL event does not steal an active lead from its current rep.
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.4 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.