<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Lead/Deal Rotation Workaround in Sales Hub Tools</title>
    <link>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/632122#M7266</link>
    <description>&lt;P&gt;I read another solution that used a handful of paid pro users to setup a multi-level round robin workflow.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Example, you have 3 pro users with a team of 9 total people who need round robin assignment;&lt;BR /&gt;Round Robin the 3 pro users; then use if/then tree to create another round robin for those same 3 users, which will activate depending on the first round robin result - now you effectively have a round robin of 9; add an assign property value at for each result which specifically sets the user to one of the 9 users.&lt;BR /&gt;&lt;BR /&gt;Such an example can be scaled to effectively work evenly for nearly any non-prime number of users.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This example can also be used to "weight" your round robin, by assigning for example 4 of the 9 results to 1 user, 4 of the 9 to another, and the remaining 1 to a 3rd user = thus getting about 45% weight for users 1 and 2, while user 3 would get about 10% of cases (1 out of 9)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This can get very messy, very quickly, especially if you are scaling up your team - but it is a workaround to this that technically can work, especially for smaller teams.&lt;/P&gt;</description>
    <pubDate>Thu, 12 May 2022 21:20:29 GMT</pubDate>
    <dc:creator>AVeley</dc:creator>
    <dc:date>2022-05-12T21:20:29Z</dc:date>
    <item>
      <title>Lead/Deal Rotation Workaround</title>
      <link>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/335776#M4405</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hoping someone could help. Recently we have built workflows with a deal owner rotation, only to realise all of the users require pro licences for this to work. This is not an option at the moment as the team is significantly expanding.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am hoping to find out if anyone out there could assist with unique workflow ideas to achieve this. We have tried:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Rotating contact owners (Same issue)&lt;/LI&gt;&lt;LI&gt;Creating a Lead ID, and values to allocate but have run into subsequential issues&lt;/LI&gt;&lt;LI&gt;Looking for plug-ins to assist&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;Looking at external platforms to push and pull data back and forth and attach owners from a spreadsheet&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea or assistance regarding this is highly appreciated.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TIA&amp;nbsp;&lt;img id="smileyvery-happy" class="emoticon emoticon-smileyvery-happy" src="https://community.hubspot.com/i/smilies/16x16_smiley-very-happy.png" alt="Smiley Very Happy" title="Smiley Very Happy" /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2020 14:37:35 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/335776#M4405</guid>
      <dc:creator>marlene00</dc:creator>
      <dc:date>2020-04-30T14:37:35Z</dc:date>
    </item>
    <item>
      <title>Re: Lead/Deal Rotation Workaround</title>
      <link>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/335827#M4411</link>
      <description>&lt;P&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/125590"&gt;@marlene00&lt;/a&gt;&amp;nbsp;- It sounds like you currently have some users with licenses already. I would highly suggest that you first contact your HubSpot Account Manager and discuss your current license structure and what you are trying to do.&amp;nbsp; You would be surprised what they can do to help you.&amp;nbsp; &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Answer 1: There is no workaround with workflows to get deals assigned within HubSpot.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Answer 2: Zapier and Automate.io can achieve what you need but may need a paid license.&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/66301"&gt;@Bryantworks&lt;/a&gt;&amp;nbsp;is an expert at setting these up and may be able to give you some insight.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2020 16:44:24 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/335827#M4411</guid>
      <dc:creator>warrendavey</dc:creator>
      <dc:date>2020-04-30T16:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: Lead/Deal Rotation Workaround</title>
      <link>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/632122#M7266</link>
      <description>&lt;P&gt;I read another solution that used a handful of paid pro users to setup a multi-level round robin workflow.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Example, you have 3 pro users with a team of 9 total people who need round robin assignment;&lt;BR /&gt;Round Robin the 3 pro users; then use if/then tree to create another round robin for those same 3 users, which will activate depending on the first round robin result - now you effectively have a round robin of 9; add an assign property value at for each result which specifically sets the user to one of the 9 users.&lt;BR /&gt;&lt;BR /&gt;Such an example can be scaled to effectively work evenly for nearly any non-prime number of users.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This example can also be used to "weight" your round robin, by assigning for example 4 of the 9 results to 1 user, 4 of the 9 to another, and the remaining 1 to a 3rd user = thus getting about 45% weight for users 1 and 2, while user 3 would get about 10% of cases (1 out of 9)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This can get very messy, very quickly, especially if you are scaling up your team - but it is a workaround to this that technically can work, especially for smaller teams.&lt;/P&gt;</description>
      <pubDate>Thu, 12 May 2022 21:20:29 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/632122#M7266</guid>
      <dc:creator>AVeley</dc:creator>
      <dc:date>2022-05-12T21:20:29Z</dc:date>
    </item>
    <item>
      <title>Re: Lead/Deal Rotation Workaround</title>
      <link>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/632157#M7267</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/305677"&gt;@AVeley&lt;/a&gt;&amp;nbsp;hope you are doing well!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for sharing &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Diana&lt;/P&gt;</description>
      <pubDate>Thu, 12 May 2022 23:01:07 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/632157#M7267</guid>
      <dc:creator>DianaGomez</dc:creator>
      <dc:date>2022-05-12T23:01:07Z</dc:date>
    </item>
    <item>
      <title>Re: Lead/Deal Rotation Workaround</title>
      <link>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/773353#M8366</link>
      <description>&lt;P&gt;Rotating (round-robin) leads is possible between unpaid users using Hubspot API.&lt;BR /&gt;Need to write a small custom script/web service&lt;/P&gt;</description>
      <pubDate>Fri, 24 Mar 2023 03:56:58 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/773353#M8366</guid>
      <dc:creator>MohsanAzad</dc:creator>
      <dc:date>2023-03-24T03:56:58Z</dc:date>
    </item>
    <item>
      <title>Re: Lead/Deal Rotation Workaround</title>
      <link>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/818197#M8857</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/542394"&gt;@MohsanAzad&lt;/a&gt;, we are having a very similar problem - do you have an example you could share of the small custom script you mention?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2023 16:52:07 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/818197#M8857</guid>
      <dc:creator>VPearcy</dc:creator>
      <dc:date>2023-07-14T16:52:07Z</dc:date>
    </item>
    <item>
      <title>Re: Lead/Deal Rotation Workaround</title>
      <link>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/820151#M8891</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/572911"&gt;@VPearcy&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;Can you please elaborate on your problem? so I can share how that can be resolved.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2023 17:02:51 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/820151#M8891</guid>
      <dc:creator>MohsanAzad</dc:creator>
      <dc:date>2023-07-14T17:02:51Z</dc:date>
    </item>
    <item>
      <title>Re: Lead/Deal Rotation Workaround</title>
      <link>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/821113#M8903</link>
      <description>&lt;P&gt;Hey &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/542394"&gt;@MohsanAzad&lt;/a&gt;&amp;nbsp;hoping you can provide an example of the script you mentioned. We have many different park locations and need to restrict contact access by team (if contact is associated with NY, assign contact to someone on the NY team so only this team can see this data). Any and all advice here is appreciated!&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2023 00:24:13 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/821113#M8903</guid>
      <dc:creator>CJohnson32</dc:creator>
      <dc:date>2023-07-18T00:24:13Z</dc:date>
    </item>
    <item>
      <title>Re: Lead/Deal Rotation Workaround</title>
      <link>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/822767#M8925</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/600395"&gt;@CJohnson32&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;If you have all paid users in your Hubspot, then it can be easily managed inside Hubspot, you can assign Leads/Contacts easily by HubSpot Workflow.&lt;BR /&gt;&lt;BR /&gt;but if all your Hubspot users are not Paid (Sales Professional) then you would need to use Hubspot API, check every 1 or 5 minutes that if there is new Contact Created in Hubspot (See Hubspot API documentation to get recent contacts) and check the values of the field and apply the conditions.&lt;BR /&gt;&lt;BR /&gt;if the Contact is from the State of NY then assign it to Team A user Abc&lt;BR /&gt;else Assign it to Team Z user Xyz&lt;BR /&gt;(or whatever conditions and business logic you want to apply)&lt;BR /&gt;&lt;BR /&gt;Then update that contact using API with a new Owner ID for that record.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Mohsan&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jul 2023 16:37:32 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/822767#M8925</guid>
      <dc:creator>MohsanAzad</dc:creator>
      <dc:date>2023-07-20T16:37:32Z</dc:date>
    </item>
    <item>
      <title>Re: Lead/Deal Rotation Workaround</title>
      <link>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/1247016#M12538</link>
      <description>&lt;P&gt;You're definitely not alone — "rotate owner" in HubSpot gets annoying fast when you don't want to pay for Pro seats for everyone who needs to be in the rotation. The most practical workaround I've seen is to handle the round-robin logic outside HubSpot and just update the record owner through the API.&lt;/P&gt;&lt;P&gt;It doesn't require heavy infrastructure. Basically you set up a webhook (or a lightweight polling job every few minutes) that fires when a new record is created. You keep a simple pointer somewhere — could be a key-value store, a database, even a spreadsheet — that tracks whose turn it is for each team or pipeline. When a new record comes in, you read the pointer, pick the next owner from the list (and optionally skip anyone who's out of office if you have that data), update the owner via HubSpot's API, then bump the pointer. Logging each assignment with the record ID, chosen owner, and timestamp makes it easy to audit and debug later.&lt;/P&gt;&lt;P&gt;If you can share a few details, I can sketch out the simplest version that would work for your case: Are you rotating deals or contacts/leads? Where are these records coming from — manual creation, forms, imports, an integration? And do you only want to assign when the owner field is empty, or overwrite existing owners too?&lt;/P&gt;&lt;P&gt;Quick disclosure: I'm building a small starter-friendly router called NextUp that does exactly this — pointer-based round robin with audit logs, focused on record owner routing rather than workflow hacks. The pattern I described above is basically what it does under the hood.&lt;/P&gt;</description>
      <pubDate>Sat, 31 Jan 2026 03:08:17 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/1247016#M12538</guid>
      <dc:creator>kepan</dc:creator>
      <dc:date>2026-01-31T03:08:17Z</dc:date>
    </item>
    <item>
      <title>Re: Lead/Deal Rotation Workaround</title>
      <link>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/1247017#M12539</link>
      <description>&lt;P class=""&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/572911"&gt;@VPearcy&lt;/a&gt; — yeah, the "small script" approach is pretty much what you'd expect: listen for new records (webhooks or polling), look up a stored pointer to see whose turn it is, update the owner through the HubSpot API, and log the decision so you have a clear trail of why each record went where it did.&lt;/P&gt;&lt;P class=""&gt;Happy to sketch out a more concrete example if you can tell me a bit more about your setup. What object are you assigning — contacts, deals, or leads? What triggers the assignment — new record creation, form submission, import, something else? And should it only assign when the owner field is empty, or is it okay to overwrite existing owners?&lt;/P&gt;&lt;P class=""&gt;If you can also give me a rough sense of volume (like 10 a day vs 1,000 a day), I can outline the flow and what the pointer and logging setup would look like.&lt;/P&gt;&lt;P class=""&gt;Quick disclosure: I'm building a starter-friendly router called NextUp that does exactly this — strict round robin with audit logs using a pointer-based approach. Same idea under the hood.&lt;/P&gt;</description>
      <pubDate>Sat, 31 Jan 2026 03:10:35 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Hub-Tools/Lead-Deal-Rotation-Workaround/m-p/1247017#M12539</guid>
      <dc:creator>kepan</dc:creator>
      <dc:date>2026-01-31T03:10:35Z</dc:date>
    </item>
  </channel>
</rss>

