How can I change the assigned user in an incoming webhook for Bitrix 24? Alternatively, how can I configure the webhook to assign a different responsible person when loading leads?
Changing the assigned user in Bitrix24 webhooks is essential for proper lead distribution and team workload management. You can modify responsible persons through webhook URL manipulation, automation rules, PHP scripts, or manual methods depending on your technical requirements and Bitrix24 plan. Understanding these techniques allows you to streamline your CRM processes and ensure leads are assigned to the most appropriate team members.
Contents
- Understanding Bitrix24 Webhooks and Responsible Person Assignment
- Changing Responsible Person Through Webhook URL Modification
- Using ONCRMLEADUPDATE Webhook for Automatic Assignment
- Configuring Automation Rules for Responsible Person Changes
- Implementing PHP Scripts for Lead Distribution
- Manual and Bulk Methods for Changing Responsible Persons
- Sources
- Conclusion
Understanding Bitrix24 Webhooks and Responsible Person Assignment
Bitrix24 webhooks serve as automated communication channels between your CRM and external systems, allowing data to flow seamlessly. When webhooks create or update leads, the default behavior typically assigns responsibility to the webhook’s associated user or follows predefined business logic. However, many organizations require more sophisticated assignment strategies to distribute work evenly among sales team members or ensure leads reach specialists based on criteria like product type, geographic region, or deal size.
The responsible person assignment directly impacts lead response times, conversion rates, and overall team productivity. Without proper automation, you risk overloading specific team members while others remain underutilized. Bitrix24’s flexible webhook system offers multiple approaches to customize this assignment process, ranging from simple configuration changes to advanced programming solutions.
Webhooks in Bitrix24 follow a specific URL structure: [account].bitrix24.com/rest/[user_id]/[secret_key]/[method].json?[parameters]. The user ID in this URL determines which account the webhook acts on behalf of, making it a critical factor in responsible person assignment. Understanding this structure is fundamental to implementing effective lead distribution strategies.
Changing Responsible Person Through Webhook URL Modification
You can directly modify the user associated with a Bitrix24 webhook by editing the numeric user ID in the webhook URL. This ID represents the account on whose behalf the webhook operates, so changing it to another user’s ID will effectively make the webhook act as that user. For example, if your current webhook URL contains /rest/1/ where “1” is the original user ID, you can change it to /rest/5/ to assign webhook operations to user ID 5.
This approach is particularly useful when you need to switch the responsible person for all webhook operations without reconfiguring the entire webhook. Simply locate the user ID in the webhook URL and replace it with the desired team member’s ID. You can find user IDs in Bitrix24 by navigating to “Settings” → “Users” and selecting the appropriate profile.
For assigning different responsible persons to leads created by webhooks, you can add a “responsible” query parameter to the outbound webhook or automation-rule URL with the target user’s ID. This parameter can then be read and applied to the lead’s responsible field during the webhook processing. The format would be: [account].bitrix24.com/rest/[user_id]/[secret_key]/crm.lead.add.json?responsible=[target_user_id].
While this method provides quick control over webhook responsible persons, it’s important to note that it affects all operations performed by that webhook. For more granular control where different leads should go to different team members, consider implementing the automation rules or PHP script methods described in subsequent sections.
Using ONCRMLEADUPDATE Webhook for Automatic Assignment
The ONCRMLEADUPDATE webhook available on all Bitrix24 plans provides a powerful mechanism for automatically assigning different responsible persons when loading leads. This webhook triggers whenever a lead is updated and returns a JSON payload containing the new responsible user ID, allowing you to implement sophisticated lead distribution algorithms.
A common implementation involves creating a PHP script that retrieves all responsible users, counts active leads for each team member, and selects the user with the fewest leads. This balanced distribution approach prevents any single team member from becoming overloaded while ensuring equal opportunity across the sales team. The script would return the selected user ID in the response, which Bitrix24 then applies to the lead.
Here’s how this approach works in practice:
- Configure your Bitrix24 account to send ONCRMLEADUPDATE requests to your custom endpoint
- Your PHP script receives the webhook data with lead information
- The script queries the Bitrix24 API or your database to get current lead counts for each salesperson
- Based on your distribution algorithm (fewest leads, round-robin, etc.), the script determines the optimal responsible person
- The script returns the selected user ID in the response format expected by Bitrix24
- Bitrix24 automatically assigns the returned user ID as the responsible person for the lead
This method is particularly effective for organizations with high lead volumes and multiple sales team members. The automatic balancing ensures fair workload distribution and prevents bottlenecks in your sales pipeline. According to technical developers at Intervolga, this approach “ensures balanced lead distribution among team members and prevents overload on specific users.”
Configuring Automation Rules for Responsible Person Changes
Bitrix24’s built-in automation rules provide a no-code solution for changing responsible persons based on specific conditions and criteria. To configure this, navigate to the CRM section, select the desired item (leads, deals, contacts, etc.), and open the Automation rules tab. From there, you can create rules that automatically modify the responsible person when certain conditions are met.
Automation rules offer several distribution methods for assigning responsible persons:
- Random order: Leads are assigned randomly to available team members
- First available: The first available salesperson receives the lead
- Specified order: Leads rotate through a predefined sequence of team members
- Skip absent: The system automatically skips team members who are absent or clocked out
You can set conditions based on various criteria such as deal amount (e.g., “if deal amount over $50,000”), lead source, geographic region, product category, or custom fields. For example, you could create a rule that assigns leads for enterprise clients to your senior sales team while distributing smaller leads to junior representatives.
The “Change responsible person” action in automation rules allows you to specify different assignment methods based on your workflow requirements. This approach is ideal for organizations that want to implement lead distribution strategies without programming knowledge. According to the Bitrix24 Helpdesk, these automation rules allow you to “automatically change the responsible person for CRM entities when they reach specific stages” and can be configured to “skip absent or clocked-out employees when assigning responsible persons.”
Implementing PHP Scripts for Lead Distribution
For organizations with complex lead distribution requirements, implementing custom PHP scripts provides the most flexible solution for responsible person assignment in Bitrix24 webhooks. These scripts can integrate with external systems, consider multiple variables, and implement sophisticated algorithms that go beyond Bitrix24’s built-in automation capabilities.
A typical PHP implementation for lead distribution involves several key components:
- Webhook Receiver: Create a script that accepts incoming webhook requests from Bitrix24 and validates the data
- Distribution Algorithm: Implement your lead distribution logic (round-robin, skills-based, performance-based, etc.)
- Bitrix24 API Integration: Use the Bitrix24 REST API to query current lead assignments and update responsible persons
- Response Handler: Format the response according to Bitrix24’s webhook requirements
For balanced distribution, many implementations query all responsible users, count active leads for each, and select the user with the fewest current leads. This prevents any single team member from becoming overloaded while ensuring equal opportunity across the sales team. The script would then return the selected user ID in the response format expected by Bitrix24.
More sophisticated scripts might consider additional factors such as:
- Sales team member performance metrics and conversion rates
- Product expertise and specialization
- Geographic location and time zone
- Current workload beyond just lead count
- Availability and clock-in status
- Historical performance with similar leads
According to technical developers, these PHP implementations “retrieves all responsible users, counts active leads for each, selects the user with the fewest leads, and returns their ID in the response. This ensures balanced lead distribution among team members and prevents overload on specific users.”
Manual and Bulk Methods for Changing Responsible Persons
When automation isn’t appropriate or when you need to make one-off adjustments, Bitrix24 offers straightforward manual methods for changing responsible persons on leads and other CRM elements. For individual leads, simply open the lead record, click on the “Responsible” field, and select the new user from the dropdown menu. This immediate reassignment works well for urgent situations or when specific expertise is required.
For bulk operations, Bitrix24 provides group actions that allow you to change responsible persons across multiple leads simultaneously. Select multiple items using checkboxes or bulk selection tools, then choose the “Change responsible” group action from the menu. This method is particularly useful for reassigning entire lead batches, such as when redistributing work after team restructuring or when transitioning between sales shifts.
It’s important to note that group actions are not available for CRM web forms, meaning leads captured through web forms cannot be bulk reassigned using this method. For these cases, you would need to implement automation rules or custom scripts to handle the responsible person assignment.
The manual approach works well for:
- One-off changes where automation isn’t justified
- Urgent reassignments requiring immediate attention
- Situations where specific expertise is needed
- Testing and validation of new distribution strategies
- Periodic workload balancing across the sales team
While manual methods provide flexibility, they become impractical for organizations with high lead volumes or regular redistribution needs. In these scenarios, the automation and script-based approaches described earlier offer more scalable solutions for managing responsible person assignments in Bitrix24.
Sources
- Bitrix24 Helpdesk — Official documentation on automation rules for CRM entities: https://helpdesk.bitrix24.com/open/16145350/
- Intervolga — Technical guide on automatic lead distribution using ONCRMLEADUPDATE webhook: https://intervolgaru.com/blog/bitrix24/automatic-lead-distribution-in-bitrix24/
- SLINKOV.Design — Webhook customization techniques for user assignment: https://soloten.com/en/bitrix24-webhook-customization
- Bitrix24 Blog — Official guide on changing responsible persons in CRM: https://www.bitrix24.com/about/blogs/crm/change-the-responsible-person-in-the-crm.php
- Bitrix24 Helpdesk — Webhook URL structure and configuration documentation: https://helpdesk.bitrix24.com/open/21133100/
Conclusion
Bitrix24 offers multiple approaches for changing assigned users in webhooks and configuring responsible person assignment for incoming leads, ranging from simple URL modifications to complex PHP implementations. The optimal solution depends on your organization’s technical capabilities, lead volume, distribution requirements, and team structure.
For organizations seeking no-code solutions, Bitrix24’s built-in automation rules provide flexible options for automatic assignment based on conditions like deal amount, lead source, or geographic region. Technical teams can implement custom PHP scripts using the ONCRMLEADUPDATE webhook for sophisticated distribution algorithms that balance workloads across sales representatives.
Regardless of the method chosen, proper lead distribution is crucial for maintaining team productivity, ensuring fair work allocation, and maximizing conversion rates. By implementing the appropriate responsible person assignment strategy for your Bitrix24 webhooks, you can streamline your sales processes and improve overall operational efficiency.
Bitrix24 provides automation rules that allow you to automatically change the responsible person for CRM entities when they reach specific stages. To configure this, navigate to the CRM section, select the desired item, and open the Automation rules tab. Use the “Change responsible person” action to assign different employees based on conditions like deal amount over $50,000. You can choose between random order, first available, or specified order distribution methods, and even skip absent or clocked-out employees when assigning responsible persons.
To automatically assign a different responsible person in Bitrix24 webhooks, use the ONCRMLEADUPDATE webhook available on all plans. This webhook returns a JSON payload containing the new responsible user ID. A common PHP implementation retrieves all responsible users, counts active leads for each, selects the user with the fewest leads, and returns their ID in the response. This ensures balanced lead distribution among team members and prevents overload on specific users.
You can change the user that a Bitrix24 inbound webhook acts as by editing the numeric user ID that follows the “rest” part of the webhook URL. This ID represents the account on whose behalf the webhook operates, so changing it to another user’s ID will make the webhook act as that user. For assigning different responsible persons to leads created by webhooks, add a “responsible” query parameter to the outbound webhook or automation-rule URL with the target user’s ID, which can then be read and applied to the lead’s responsible field.
In Bitrix24, you can manually change the responsible person for any CRM element by opening the lead, deal, contact, etc., clicking the “Responsible” field, and selecting the new user. For bulk changes, select multiple items and use the group action “Change responsible.” Note that group actions are not available for CRM web forms. This straightforward approach works well for one-off changes or when you need to quickly reassign responsibility without complex automation.
Bitrix24 webhooks use a specific URL structure that includes your account address, “/rest,” user ID, secret key, method name, and optional parameters. When creating webhooks, you can use the REST request builder to select methods and parameters, and assign permissions to specific Bitrix24 tools. The webhook URL format follows: [account].bitrix24.com/rest/[user_id]/[secret_key]/[method].json?[parameters]. Understanding this structure is essential for properly configuring webhooks to modify responsible persons.
