Skip to content
Contact us
All posts

How to Set Up Round-Robin Lead Routing in HubSpot Workflows

Picture of John Hulina By   ·  2 minute read

To set up round-robin lead routing in HubSpot, use a workflow with the "Rotate leads" action (available on Sales Hub Pro and above) or, for territory-based routing, a workflow that checks contact/company properties (state, industry, company size) with branching logic that sets the record's owner accordingly. The most common failure isn't the rotation logic itself — it's leads arriving with missing or inconsistent property values that break the routing rules before they ever reach a rep.

Step-by-step: building the workflow

  1. Decide your routing model first. Pure round-robin (even distribution across a team) is different from territory-based routing (by region, industry, or company size) and from tiered routing (SMB vs. enterprise reps). Pick one before building — mixing models in a single workflow gets confusing fast.
  2. Clean the trigger properties. If you're routing by state or company size, make sure every incoming lead actually has that property populated. A workflow branch with no matching condition sends the lead nowhere, or to a default fallback nobody's watching.
  3. Build the workflow. Automation → Workflows → Create workflow → contact-based (or deal-based, depending on when you want routing to happen). Set your enrollment trigger (form submission, list membership, deal creation).
  4. Add rotation or branching. For round-robin: add the "Rotate leads" action and select your team members. For territory routing: use "If/then" branches on the relevant property, with a "Set property value" action to assign the owner in each branch.
  5. Add a fallback branch. Always include a default path for leads that don't match any territory condition — route them to a queue or a specific person rather than letting them fall through with no owner.
  6. Test with a few submissions before going live. Submit test leads matching each branch condition and confirm ownership assigns correctly, including the fallback.

Common mistakes

The most common issue is routing on a property that isn't reliably populated — state or country left blank on a form, or an industry field only filled in for some lead sources. The workflow logic is correct, but leads silently miss every branch. A second common mistake is building round-robin rotation without accounting for reps who are out or over capacity: HubSpot's rotate action distributes evenly regardless of a rep's current workload unless you actively manage the team list. Third, teams often set up routing once and never revisit it as the sales team changes — a workflow still routing to someone who left the company three months ago is a surprisingly common find.

When to bring in a pro

Simple round-robin across a small, stable team is very doable in-house. Bring in a consultant when you need multi-tier routing (SMB vs. mid-market vs. enterprise, each with different logic), routing that spans both contacts and companies with different owners, or when your current routing has been running for a while and needs an audit to find where leads are falling through. Get in touch to talk through your routing setup.

FAQ

Does round-robin routing require Sales Hub Pro?
The native "Rotate leads" workflow action requires Sales Hub Pro or above. On lower tiers, teams typically build a manual rotation using a counter property and branching logic instead.

Can I route both contacts and deals?
Yes, but they need separate workflows — a contact-based workflow sets the contact owner, and a deal-based workflow (often triggered on deal creation) sets the deal owner, which may or may not match.

What happens to a lead if no branch condition matches?
It falls through to whatever your fallback branch does — if you haven't built one, the lead simply doesn't get an owner assigned by that workflow.

How do I handle reps going on vacation or leaving the team?
You need to manually update the rotation list or branching logic when team membership changes — HubSpot doesn't automatically detect availability.

Written by John Hulina, founder of CRM Assist and leader of the Orange County HubSpot User Group. John is also a CRMmys awards judge and builds HubSpot automation for B2B revenue teams.