The Workflow Library

Library / Lead routing / lead-routing-026

Route leads from paid ads (Facebook/LinkedIn lead ads) into rep queue

Lead routingContactMarketing Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. A lead captured through a Facebook or LinkedIn native lead ad form reaches the right rep queue for the product or campaign it came from, instead of sitting in a generic ads bucket.

Workflow map Enrollment, branches and actions at a glance lead-routing-026
flowchart TD
    A[Lead ad form submitted] --> B{Campaign maps to which product?}
    B -->|Product A| C[Rotate to Product A reps]
    B -->|Product B| D[Rotate to Product B reps]
    B -->|unmapped| E[Rotate to General paid-ads pool + notify ops]
    C --> F[Set routed date, notify, create call task]
    D --> F
    E --> F
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when the Facebook Lead Ads and/or LinkedIn Lead Gen Forms integration is connected and mapped to HubSpot forms.
  • UseUse it when different ad campaigns represent different product lines or offers that should route to different specialist reps.
  • SkipDo not use it if all paid-ads leads go to the same generalist pool regardless of campaign; a plain rotation (lead-routing-002) is simpler.
  • SkipDo not use it as your only lead-quality gate. Native lead ad forms pre-fill from the platform's own profile data with no validation, pair this with a data-quality check, see Known pitfalls.
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.14 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.