Add a New Action bizproc.activity.add
Choose a tool for developing with an AI agent:
- use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
- use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation
Scope:
bizprocWho can execute the method: administrator
The bizproc.activity.add 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 type properties in PROPERTIES.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
CODE* |
Internal identifier of the action. It is 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:
By default, the parameter is empty, which is equivalent to waiting for a response from the application. The action does not wait for a response only when explicitly set to |
|
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 for restricting the action by document type and edition. 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 |
Parameter requirement. Possible values:
|
|
Multiple |
Parameter multiplicity. 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);
}
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.bizproc.activity.add(
code="md5_action",
handler="https://example.com/ping.php",
name={
"ru": "MD5 generator",
"en": "MD5 generator",
},
auth_user_id=1,
use_subscription=True,
description={
"ru": "The action returns the MD5 hash of the input parameter",
"en": "Activity returns MD5 hash of input parameter",
},
properties={
"inputString": {
"Name": {
"ru": "Input string",
"en": "Input string",
},
"Description": {
"ru": "Enter the string you want to hash",
"en": "Input string for hashing",
},
"Type": "string",
"Required": "Y",
"Multiple": "N",
"Default": "{=Document:NAME}",
},
},
return_properties={
"outputString": {
"Name": {
"ru": "MD5",
"en": "MD5",
},
"Type": "string",
"Multiple": "N",
"Default": None,
},
},
document_type=(
"lists",
"BizprocDocument",
"iblock_164",
),
filter={
"INCLUDE": [
[
"lists",
],
],
},
).response
result = bitrix_response.result
print(result)
except BitrixAPIError as error:
print(
"Bitrix API error",
f"error: {error.error}",
f"error_description: {error.error_description}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK error: {error.message}")
except Exception as error:
print(f"Unexpected 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>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "bizproc.activity.add", b24.Params{
"CODE": "md5_action",
"HANDLER": "https://your_domain/ping.php",
"AUTH_USER_ID": 1,
"USE_SUBSCRIPTION": "Y",
"NAME": b24.Params{
"en": "MD5 generator",
},
"DESCRIPTION": b24.Params{
"en": "Activity returns MD5 hash of input parameter",
},
"PROPERTIES": b24.Params{
"inputString": b24.Params{
"Name": b24.Params{
"en": "Input string",
},
"Description": b24.Params{
"en": "Input string for hashing",
},
"Type": "string",
"Required": "Y",
"Multiple": "N",
"Default": "{=Document:NAME}",
},
},
"RETURN_PROPERTIES": b24.Params{
"outputString": b24.Params{
"Name": b24.Params{
"ru": "MD5",
"en": "MD5",
},
"Type": "string",
"Multiple": "N",
"Default": nil,
},
},
"DOCUMENT_TYPE": []string{"lists", "BizprocDocument", "iblock_164"},
"FILTER": b24.Params{
"INCLUDE": []any{
[]string{"lists"},
},
},
})
if err != nil {
return fmt.Errorf("bizproc.activity.add: %w", err)
}
var ok bool
if err := json.Unmarshal(res.Result, &ok); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println("done:", ok)
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 request execution time |
Error Handling
HTTP Status: 400
{
"error": "ERROR_ACTIVITY_VALIDATION_FAILURE",
"error_description": "Empty activity code!"
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
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! |
Action 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! |
Action with this code is already installed |
|
|
Activity or Robot already added! |
Action has already been added |
|
|
Activity save error! |
Failed to save action, system error |
Statuses and System Error Codes
HTTP Status: 4xx, 5xx
The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — |
|
|
|
No active webhook with the specified user identifier and secret code was found |
|
|
|
No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope |
|
|
|
The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
The public part of the site is closed. To open it 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 |