Add a New Action bizproc.activity.add
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 adds a new action for use in workflows.
The method works only in the context of an application.
Each document generates its own set of field types. For example, in CRM, there is a field of type Address UF:address. To use this field type in your actions, specify the CRM document type in DOCUMENT_TYPE and describe the field properties in PROPERTIES.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
CODE* |
Internal identifier of the action. It must be unique within the application. Allowed characters are |
|
HANDLER* |
URL to which the action will send data via the Bitrix24 queue server. The link must have the same domain where the application is installed |
|
AUTH_USER_ID |
Identifier of the user whose token will be passed to the application |
|
USE_SUBSCRIPTION |
Should the action wait for a response from the application. Possible values:
|
|
NAME* |
Name of the action. It can be a string or an associative array of localized strings like:
|
|
DESCRIPTION |
Description of the action. It can be a string or an associative array of localized strings like:
|
|
PROPERTIES |
Object with action parameters. Contains objects, each describing a parameter of the action. The system name of the parameter must start with a letter and can contain characters |
|
RETURN_PROPERTIES |
Object with additional results of the action. Contains objects, each describing a parameter of the action. This parameter controls whether the action can wait for a response from the application and work with the data that will come in the response. The system name of the parameter must start with a letter and can contain characters |
|
DOCUMENT_TYPE |
Document type that will determine the data types for the
Possible value options:
|
|
FILTER |
Object with rules to restrict the action by document type and edition. It can contain keys:
Each rule in the array can be a string or an array of document types in full or partial form. To restrict the action by Bitrix24 edition, specify:
Examples:
|
|
USE_PLACEMENT |
Allows opening additional settings for the action in the application slider. Possible values:
|
|
PLACEMENT_HANDLER* |
URL of the placement handler on the application side. Required if |
Object PROPERTY
|
Name |
Description |
|
Name |
Name of the parameter |
|
Description |
Description of the parameter |
|
Type |
Type of the parameter. Basic values:
|
|
Options |
Array of values for the parameter of type list
|
|
Required |
Requirement of the parameter. Possible values:
|
|
Multiple |
Multiplicity of the parameter. Possible values:
|
|
Default |
Default value of the parameter |
Examples of Objects
Below are examples of PROPERTY objects for different parameter types.
-
select'docType': { 'Name': { 'de': 'Dokumenttyp', 'en': 'Document type' }, 'Required': 'Y', 'Multiple': 'N', 'Default': 'PDF', 'Type': 'select', 'Options': { 'pdf': 'PDF', 'docx': 'DOCX' } } -
bool'saveDoc': { 'Name': { 'de': 'Dokument speichern', 'en': 'Save document' }, 'Description': { 'de': 'Ordnungsnummer zuweisen', 'en': 'Assign a sequential number' }, 'Type': 'bool', 'Required': 'Y', 'Multiple': 'N', 'Default': 'Y' } -
file'attachment': { 'Name': { 'de': 'Datei', 'en': 'File' }, 'Description': { 'de': 'Datei zum Senden', 'en': 'File to send' }, 'Type': 'file', 'Required': 'N', 'Multiple': 'Y' } -
string'Parameters': { 'Name': { 'de': 'Vorlagenparameter', 'en': 'Template\'s parameters' }, 'Description': { 'de': 'ParamID={=ParamValue}', 'en': 'ParamID={=ParamValue}' }, 'Type': 'string', 'Required': 'N', 'Multiple': 'Y' }
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"CODE":"md5_action","HANDLER":"https://your_domain/ping.php","AUTH_USER_ID":1,"USE_SUBSCRIPTION":"Y","NAME":{"de":"MD5 Generator","en":"MD5 generator"},"DESCRIPTION":{"de":"Die Aktion gibt den MD5-Hash des Eingabeparameters zurück","en":"Activity returns MD5 hash of input parameter"},"PROPERTIES":{"inputString":{"Name":{"de":"Eingabestring","en":"Input string"},"Description":{"de":"Geben Sie den String ein, den Sie hashen möchten","en":"Input string for hashing"},"Type":"string","Required":"Y","Multiple":"N","Default":"{=Document:NAME}"}},"RETURN_PROPERTIES":{"outputString":{"Name":{"de":"MD5","en":"MD5"},"Type":"string","Multiple":"N","Default":null}},"DOCUMENT_TYPE":["lists","BizprocDocument","iblock_164"],"FILTER":{"INCLUDE":[["lists"]]},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/bizproc.activity.add
try
{
const response = await $b24.callMethod(
'bizproc.activity.add',
{
'CODE': 'md5_action',
'HANDLER': 'https://your_domain/ping.php',
'AUTH_USER_ID': 1,
'USE_SUBSCRIPTION': 'Y',
'NAME': {
'de': 'MD5 Generator',
'en': 'MD5 generator'
},
'DESCRIPTION': {
'de': 'Die Aktion gibt den MD5-Hash des Eingabeparameters zurück',
'en': 'Activity returns MD5 hash of input parameter'
},
'PROPERTIES': {
'inputString': {
'Name': {
'de': 'Eingabestring',
'en': 'Input string'
},
'Description': {
'de': 'Geben Sie den String ein, den Sie hashen möchten',
'en': 'Input string for hashing'
},
'Type': 'string',
'Required': 'Y',
'Multiple': 'N',
'Default': '{=Document:NAME}'
}
},
'RETURN_PROPERTIES': {
'outputString': {
'Name': {
'de': 'MD5',
'en': 'MD5'
},
'Type': 'string',
'Multiple': 'N',
'Default': null
}
},
'DOCUMENT_TYPE': ['lists', 'BizprocDocument', 'iblock_164'],
'FILTER': {
INCLUDE: [
['lists']
]
}
}
);
const result = response.getData().result;
alert("Success: " + result);
}
catch( error )
{
alert("Error: " + error);
}
try {
$response = $b24Service
->core
->call(
'bizproc.activity.add',
[
'CODE' => 'md5_action',
'HANDLER' => 'https://your_domain/ping.php',
'AUTH_USER_ID' => 1,
'USE_SUBSCRIPTION' => 'Y',
'NAME' => [
'de' => 'MD5 Generator',
'en' => 'MD5 generator'
],
'DESCRIPTION' => [
'de' => 'Die Aktion gibt den MD5-Hash des Eingabeparameters zurück',
'en' => 'Activity returns MD5 hash of input parameter'
],
'PROPERTIES' => [
'inputString' => [
'Name' => [
'de' => 'Eingabestring',
'en' => 'Input string'
],
'Description' => [
'de' => 'Geben Sie den String ein, den Sie hashen möchten',
'en' => 'Input string for hashing'
],
'Type' => 'string',
'Required' => 'Y',
'Multiple' => 'N',
'Default' => '{=Document:NAME}'
]
],
'RETURN_PROPERTIES' => [
'outputString' => [
'Name' => [
'de' => 'MD5',
'en' => 'MD5'
],
'Type' => 'string',
'Multiple' => 'N',
'Default' => null
]
],
'DOCUMENT_TYPE' => ['lists', 'BizprocDocument', 'iblock_164'],
'FILTER' => [
'INCLUDE' => [
['lists']
]
]
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error: ' . $e->getMessage();
}
BX24.callMethod(
'bizproc.activity.add',
{
'CODE': 'md5_action',
'HANDLER': 'https://your_domain/ping.php',
'AUTH_USER_ID': 1,
'USE_SUBSCRIPTION': 'Y',
'NAME': {
'de': 'MD5 Generator',
'en': 'MD5 generator'
},
'DESCRIPTION': {
'de': 'Die Aktion gibt den MD5-Hash des Eingabeparameters zurück',
'en': 'Activity returns MD5 hash of input parameter'
},
'PROPERTIES': {
'inputString': {
'Name': {
'de': 'Eingabestring',
'en': 'Input string'
},
'Description': {
'de': 'Geben Sie den String ein, den Sie hashen möchten',
'en': 'Input string for hashing'
},
'Type': 'string',
'Required': 'Y',
'Multiple': 'N',
'Default': '{=Document:NAME}'
}
},
'RETURN_PROPERTIES': {
'outputString': {
'Name': {
'de': 'MD5',
'en': 'MD5'
},
'Type': 'string',
'Multiple': 'N',
'Default': null
}
},
'DOCUMENT_TYPE': ['lists', 'BizprocDocument', 'iblock_164'],
'FILTER': {
INCLUDE: [
['lists']
]
}
},
function(result)
{
if(result.error())
alert("Error: " + result.error());
else
alert("Success: " + result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'bizproc.activity.add',
[
'CODE' => 'md5_action',
'HANDLER' => 'https://your_domain/ping.php',
'AUTH_USER_ID' => 1,
'USE_SUBSCRIPTION' => 'Y',
'NAME' => [
'de' => 'MD5 Generator',
'en' => 'MD5 generator'
],
'DESCRIPTION' => [
'de' => 'Die Aktion gibt den MD5-Hash des Eingabeparameters zurück',
'en' => 'Activity returns MD5 hash of input parameter'
],
'PROPERTIES' => [
'inputString' => [
'Name' => [
'de' => 'Eingabestring',
'en' => 'Input string'
],
'Description' => [
'de' => 'Geben Sie den String ein, den Sie hashen möchten',
'en' => 'Input string for hashing'
],
'Type' => 'string',
'Required' => 'Y',
'Multiple' => 'N',
'Default' => '{=Document:NAME}'
]
],
'RETURN_PROPERTIES' => [
'outputString' => [
'Name' => [
'de' => 'MD5',
'en' => 'MD5'
],
'Type' => 'string',
'Multiple' => 'N',
'Default' => null
]
],
'DOCUMENT_TYPE' => ['lists', 'BizprocDocument', 'iblock_164'],
'FILTER' => [
'INCLUDE' => [
['lists']
]
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1738148752.692647,
"finish": 1738148752.749058,
"duration": 0.056411027908325195,
"processing": 0.018677949905395508,
"date_start": "2025-01-29T14:05:52+01:00",
"date_finish": "2025-01-29T14:05:52+01:00",
"operating_reset_at": 1738149352,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Returns |
|
time |
Information about the execution time of the request |
Error Handling
HTTP Status: 400
{
"error": "ERROR_ACTIVITY_VALIDATION_FAILURE",
"error_description": "Empty activity code!"
}
|
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 a non-administrator |
|
|
Empty data! |
Required fields are not specified |
|
|
Empty activity code! |
Activity code is not specified |
|
|
Wrong activity code! |
Invalid activity code |
|
|
Unsupported handler protocol |
Invalid handler protocol http, https |
|
|
Wrong handler URL |
Invalid handler URL |
|
|
Empty activity NAME! |
Activity name is not specified |
|
|
Wrong properties array! |
Incorrectly filled |
|
|
Wrong property key ! |
Invalid property identifier |
|
|
Empty property NAME ! |
Property name is not specified |
|
|
Wrong activity FILTER! |
Invalid filter |
|
|
Wrong activity DOCUMENT_TYPE! |
Invalid |
|
|
Activity or Robot already installed! |
An action with this code is already installed |
|
|
Activity or Robot already added! |
The action has already been added |
|
|
Activity save error! |
Failed to save the action, system error |
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 Actions: Overview of Methods
- Update Action bizproc.activity.update
- Get a List of Application Actions bizproc.activity.list
- Delete Action bizproc.activity.delete
- Write Information to the Business Process Log bizproc.activity.log