Delete Registered Robot bizproc.robot.delete
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Scope:
bizprocWho can execute the method: administrator
This method removes a robot registered by the application.
It only works in the context of the application.
When the application is deleted or updated, the associated robots are removed from the list of robots. If the robot is in use, it is blocked and can only be removed from the workflow. Upon reinstalling the application, the robot becomes available again.
Method Parameters
|
Name |
Description |
|
CODE* |
Symbolic identifier of the application robot |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"CODE":"test_robot","auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/bizproc.robot.delete
try
{
const response = await $b24.callMethod(
'bizproc.robot.delete',
{
'CODE': 'test_robot'
}
);
const result = response.getData().result;
alert("Success: " + result);
}
catch( error )
{
alert('Error: ' + error);
}
try {
$robotCode = 'your_robot_code_here'; // Replace with the actual robot code
$result = $serviceBuilder
->getBizProcScope()
->robot()
->delete($robotCode);
if ($result->isSuccess()) {
print("Robot deleted successfully.");
} else {
print("Failed to delete robot.");
}
} catch (Throwable $e) {
print("Error: " . $e->getMessage());
}
BX24.callMethod(
'bizproc.robot.delete',
{
'CODE': 'test_robot'
},
function(result) {
if(result.error())
alert('Error: ' + result.error());
else
alert("Success: " + result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'bizproc.robot.delete',
[
'CODE' => 'test_robot'
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result": true,
"time": {
"start": 1738150149.8462,
"finish": 1738150149.8894911,
"duration": 0.043291091918945312,
"processing": 0.0053689479827880859,
"date_start": "2025-01-29T14:29:09+01:00",
"date_finish": "2025-01-29T14:29:09+01:00",
"operating_reset_at": 1738150749,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Returns |
|
time |
Information about the request execution time |
Error Handling
HTTP status: 400
{
"error": "ERROR_ACTIVITY_NOT_FOUND",
"error_description": "Activity or Robot not found!"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Error Codes
|
Code |
Error Message |
Description |
|
|
Application context required |
Application context is required |
|
|
Access denied! |
Method executed by non-administrator |
|
|
Empty activity code! |
Robot code not specified |
|
|
Wrong activity code! |
Invalid robot code |
|
|
Activity or Robot not found! |
Robot not found |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the portal administrator has restricted access to this application to specific users only |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the "Temporary closure of the public part of the site" option. Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Application Automation Rules: Overview of Methods
- Register a New Automation Rule bizproc.robot.add
- Update Fields of the Automation Rule bizproc.robot.update
- Get a list of registered application robots bizproc.robot.list
- Return Parameters to Action or Automation Rule bizproc.event.send