Workflow Action - Assign To User

Modified on: Thu, 24 Jul, 2025 at 7:25 PM

This article provides a detailed guide to the “Assign To User” workflow action, a feature designed to simplify contact assignment within your workflows. You’ll learn what this action does, its key benefits, a step-by-step configuration process, and real-world use cases to help you leverage it effectively.


TABLE OF CONTENTS


What is "Assign To User" Workflow Action


The “Assign To User” workflow action allows you to automatically assign contacts to one or more team members (Users) based on predefined criteria. It supports both single-user assignments and multi-user distribution using methods like round-robin or custom traffic splits. This action ensures balanced workload distribution, enhances tracking, and enables streamlined team collaboration. Whether you’re assigning leads, tickets, or tasks, this feature is designed to adapt to your specific workflow needs.


Key Benefits of "Assign To User" Workflow Action


  • Automated Assignments: Save time and effort by eliminating the need for manual contact assignment.

  • Fair Distribution: Use round-robin or equal distribution methods to balance workload among team members.

  • Custom Allocation: Assign contacts unevenly based on team capacity or seniority to maximize efficiency.

  • Improved Tracking: Ensure accountability by clearly defining who is responsible for each contact.

  • Flexible Workflows: Adapt the feature for various use cases, from sales lead management to customer support.

Adding "Assign To User" Action


Open the workflow builder, Click the “+” icon to add a new action, and select “Assign To User.”


Configuring "Assign User" Workflow Action


Action Name


Provide a descriptive name for the action (e.g., “Assign to Agents in California”) so it’s easy to identify in the workflow.


Select the Users


Use the dropdown menu to choose one or more users for the task to be assigned.

  • Single User: All contacts are assigned to one user.

  • Multiple Users: When you select more than one user, the trigger automatically rotates between the designated users in a "round robin" for each assignment. For instance, if you choose Tom and Jane, the first trigger assigns the contact to Tom, the second trigger assigns to Jane, the third assigns to Tom again, and so on until all contacts have had users assigned to them.



Splitting Assignment to Users (Weighted Round Robin)


Splitting contact assignment to users evenly or unevenly distributes tasks, contacts, or leads among selected users based on predefined rules.


Distributing Equally


By selecting "Equally" under the Split Traffic option, the traffic will be distributed evenly among all the users, similar to the Round-Robin Assignment method (e.g., 1:1, 2:2, etc.). This is enabled by default until you switch to the Unevenly option.




Distributing Unevenly


Opting for the "Unevenly" option allows you to customize the traffic distribution ratio for each selected user. For instance, you could specify a ratio of 5:2, where User A receives five traffic and User B receives two traffic; therefore, User B will only receive traffic after User A has completed their fifth.


If Split Traffic is Unevenly and there are three Users with these weights:

  • Alan: 3
  • Bobby: 3
  • Charlie: 1

Then workflow trigger 1, 2, and 3 will be assigned to Alan; trigger 4, 5, and 6 will be assigned to Bobby; trigger 7 will be assigned to Charlie; then the cycle will repeat.



Only Apply to Unassigned Contacts


If the "Only Apply To Unassigned Contacts" toggle is turned off, and the trigger fires for an already assigned contact, the new task will overwrite the previous one, and the contact will be assigned to the new user.

  • Enabled: Assign contacts only if they haven’t been assigned yet.

  • Disabled: Reassign contacts even if they are already assigned.


Standard vs Dynamic User IDs


In the Users dropdown where you select one or more Users to use in the assignment, Standard is selected by default, which shows you a dropdown menu of all Users in the subaccount. If you select Dynamic the field changes to a plain text field and you can input user IDs directly or via merge tags.


Note that the Dynamic view allows you to manually enter one or more user IDs. However, the normal way to use it is to select a variable from earlier in the workflow that contains a user ID.



Where To Find User ID Manually



In order to manually obtain the user ID for your users: Go to Settings > My Staff. The user ID can be found below the user’s email address.



How To Assign Users Dynamically


In most situations you should use the Standard picker because your Assign User logic is simple and/or is defined inside a HighLevel workflow. However, some advanced users have more complex Assign User logic which is running outside HighLevel.


Example advanced Assign User case:

A digital marketing agency with several account managers serving different client tiers, training, and sometimes covering for each other.

New lead arrives → External system evaluates:
- Lead source (Google Ads, referral, cold outreach)
- Company size (employees, revenue)
- Service interest (SEO, PPC, social media)
- Geographic location

External system creates smart assignment:
- Enterprise leads → Senior Account Manager (User id #1 or #2)
- Enterprise Leads training → Standard Account Manager (User id #3)
- Mid-market leads → Standard Account Manager (User id #3, #4, or #5)
- Small business leads → Junior Account Manager (User id #6, #7, #8, or #9)
- Small business leads overflow → Standard Account Manager (User id #4 or #5)

Workflow receives inbound webhook to assign User id to contact.


Step 1: Create Workflow

Create a new workflow and add an Inbound Webhook Trigger, a Find Contact Action, and an Assign User Action.


Step 2: Send Setup Webhook

Setup the Inbound Webhook by using your system of choice to send an example to the URL provided. In this case we used https://reqbin.com/ for a quick free test. Setup a user_id param and a contact_email param. When you see "status: success: test request received" you can return to the Inbound Webhook Trigger.




Step 3: Configure Inbound Webhook Trigger

Return to the Inbound Webhook Trigger, find the successful request, check the mapping, and save the trigger. Now that Inbound Webhook Trigger and its query parameters will be available later in the workflow.




Step 4: Configure Find Contact Action

Edit the Find Contact Action by selecting the User > Email field and then mapping it to the Inbound Webhook > QueryParams > contact_email field.




Step 5: Configure Assign User Action

Edit the Assign User Action by switching from Standard to Dynamic. Then In the merge field picker select the Inbound Webhook Trigger > QueryParams > user_id field.




Step 6: Test & Save

Make sure to test the workflow under a variety of conditions. When you're satisfied, make sure to save it and publish when you're read for it to go live.



Frequently Asked Questions


What is the purpose of the “Assign to User” action in a workflow?

The “Assign to User” action allows you to automatically assign contacts to specific team members, ensuring efficient workload management and tracking.



What happens if I select only one user in the “Assign to User” action?

If you choose one user, all contacts triggered by the workflow will be assigned to that user, and the assignment won’t rotate to other users.



Can I use the “Assign to User” action without turning on the “Only Apply to Unassigned Contacts” toggle?

Yes, but any previously assigned contact may be reassigned to a new user when the workflow trigger fires.



What is the difference between Round-Robin Assignment and Equally Split Traffic?

Round-Robin rotates assignments one at a time among users. Equally Split Traffic ensures users receive an equal number of assignments over time.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article