The Workflow Library

Library / Lead routing / lead-routing-028

Route company-level lead to whoever owns an associated open deal

Lead routingCompanySales Hub ProfessionalIntermediate~35 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Sales Hub Professional, and one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written.

Outcome. A new, unowned company that already has an open deal in progress goes straight to that deal's owner, instead of a fresh round-robin pick who has no context on the existing conversation.

Workflow map Enrollment, branches and actions at a glance lead-routing-028
flowchart TD
    A[Company created / owner unknown] --> B{Associated open deals?}
    B -->|Exactly 1| C[Copy deal owner to company owner]
    B -->|2 or more| D[Notify sales ops, add to Needs manual routing]
    B -->|None| E[Rotate to Company fallback queue]
    C --> F[Set routed date, notify new owner]
    E --> F
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when new company records can appear unowned (through a form, import, or enrichment tool) while a deal already exists and is being actively worked by someone.
  • UseUse it when your deal pipeline stages clearly separate "open" from "closed" so the branch condition can target real stage values.
  • SkipDo not use it if a company can plausibly have several genuinely active deals owned by different reps; that ambiguity needs a human decision, not an automatic pick, see Steps.
  • SkipDo not use it as a substitute for lead-routing-001 style routing on brand-new companies with no deal history at all; this fiche only helps once a deal already exists.
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.9 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.