Skip to content

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

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Marketing Hub Professional.

Contact14 stepsUpdated for HubSpot seat pricing
OutcomeA 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 maplead-routing-026
Lead ad form submitted leads to Campaign maps to which product?. Campaign maps to which product? leads to Product A: Rotate to Product A reps; Product B: Rotate to Product B reps; unmapped: Rotate to General paid-ads pool + notify ops. Rotate to Product A reps leads to Set routed date, notify, create call task. Rotate to Product B reps leads to Set routed date, notify, create call task. Rotate to General paid-ads pool + notify ops leads to Set routed date, notify, create call task. Product A Product B unmapped Lead ad form submitted Campaign maps to which product? Rotate to Product A reps Rotate to Product B reps Rotate to General paid-ads pool + notify ops Set routed date, notify, create call task
Lead ad form submitted leads to Campaign maps to which product?. Campaign maps to which product? leads to Product A: Rotate to Product A reps; Product B: Rotate to Product B reps; unmapped: Rotate to General paid-ads pool + notify ops. Rotate to Product A reps leads to Set routed date, notify, create call task. Rotate to Product B reps leads to Set routed date, notify, create call task. Rotate to General paid-ads pool + notify ops leads to Set routed date, notify, create call task. Lead ad form submitted Campaign maps to which product? Product A Rotate to Product A reps Product B Rotate to Product B reps unmapped Rotate to General paid-ads pool + notify ops Set routed date, notify, create call task

When to use it, when not to

Use it

  • Use it when the Facebook Lead Ads and/or LinkedIn Lead Gen Forms integration is connected and mapped to HubSpot forms.
  • Use it when different ad campaigns represent different product lines or offers that should route to different specialist reps.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 14 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 4 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Lead routing spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library