Update Business Process Template bizproc.workflow.template.update
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
This method updates a business process template.
It allows you to update templates that were created using the bizproc.workflow.template.add method. These templates are tied to the application and can only be updated in the context of the same application that created them.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
ID* |
Identifier of the template to be updated |
|
FIELDS* |
Object with fields of the business process template. You can update the fields: |
FIELDS Parameter
|
Name |
Description |
|
NAME |
Name of the template |
|
DESCRIPTION |
Description of the template |
|
TEMPLATE_DATA |
Content of the file with the business process template in More details on how to transfer files can be found in the article How to Update and Delete Files |
|
AUTO_EXECUTE |
Auto-execution settings for the template. Can have the following values:
Default is |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ID":525,"FIELDS":{"NAME":"Display Time","DESCRIPTION":"Template shows a message with local and server time","AUTO_EXECUTE":0},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/bizproc.workflow.template.update
try
{
const response = await $b24.callMethod(
'bizproc.workflow.template.update',
{
ID: 525,
FIELDS: {
NAME: 'Display Time',
DESCRIPTION: 'Template shows a message with local and server time',
AUTO_EXECUTE: 0,
}
}
);
const result = response.getData().result;
console.log(result);
}
catch( error )
{
alert("Error: " + error);
}
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.bizproc.workflow.template.update(
bitrix_id=525,
fields={
"NAME": "Display the time",
"DESCRIPTION": "The template displays a message with the local and server time",
"AUTO_EXECUTE": 0,
},
).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.workflow.template.update',
[
'ID' => 525,
'FIELDS' => [
'NAME' => 'Display Time',
'DESCRIPTION' => 'Template shows a message with local and server time',
'AUTO_EXECUTE' => 0,
],
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
echo 'Error: ' . $result->error();
} else {
echo 'Success: ' . print_r($result->data(), true);
}
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error updating workflow template: ' . $e->getMessage();
}
BX24.callMethod(
'bizproc.workflow.template.update',
{
ID: 525,
FIELDS: {
NAME: 'Display Time',
DESCRIPTION: 'Template shows a message with local and server time',
AUTO_EXECUTE: 0,
}
},
function(result)
{
if(result.error())
alert("Error: " + result.error());
else
console.log(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'bizproc.workflow.template.update',
[
'ID' => 525,
'FIELDS' => [
'NAME' => 'Display Time',
'DESCRIPTION' => 'Template shows a message with local and server time',
'AUTO_EXECUTE' => 0
]
]
);
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.workflow.template.update", b24.Params{
"ID": 525,
"FIELDS": b24.Params{
"NAME": "Display Time",
"DESCRIPTION": "Template shows a message with local and server time",
"AUTO_EXECUTE": 0,
},
})
if err != nil {
return fmt.Errorf("bizproc.workflow.template.update: %w", err)
}
var value b24.ID
if err := json.Unmarshal(res.Result, &value); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println("result:", value)
Response Handling
HTTP Status: 200
{
"result": 525,
"time": {
"start": 1737534421.172673,
"finish": 1737534421.209758,
"duration": 0.037085056304931641,
"processing": 0.010869026184082031,
"date_start": "2025-01-22T11:27:01+01:00",
"date_finish": "2025-01-22T11:27:01+01:00",
"operating_reset_at": 1737535021,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Identifier of the updated business process template |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": "ERROR_TEMPLATE_NOT_OWNER",
"error_description": "You can update ONLY templates created by current application"
}
|
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 |
Access token not from the application |
|
|
Access denied! |
Method was not executed by an administrator |
|
|
No fields to update. |
No fields specified for update |
|
|
Workflow template not found. |
Template with the specified |
|
|
You can update ONLY templates created by current application |
This template cannot be edited through this application |
|
|
Empty template name! |
Empty template name specified |
|
|
Incorrect field AUTO_EXECUTE! |
Invalid auto-execution code specified |
|
|
Incorrect field TEMPLATE_DATA! |
Invalid template data specified |
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 |