Add a New Sales Funnel crm.category.add
Scope:
crmWho can execute the method: any user with administrative access to the CRM section
This method creates a new sales funnel (direction) for the CRM object type with the identifier entityTypeId.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
entityTypeId* |
Identifier of the system or user-defined type of the CRM entity for which the new funnel will be created |
|
fields* |
Field values (detailed description provided below) for adding a new funnel in the form of a structure:
|
Parameter fields
Required parameters are marked with *
|
Name |
Description |
|
name* |
Name of the funnel. The name can be:
Defaults to |
|
sort |
Sort index. Cannot be negative. If a value less than zero is passed to Defaults to |
|
isDefault |
Indicates whether the funnel is the default funnel. Can have values:
Defaults to In deals, the Restrictions on changing the
If the display of directions in the interface is disabled for an existing SPA, working with directions via REST is still possible. |
Code Examples
Create a new default funnel in the SPA with entityTypeId = 1152.
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"entityTypeId": 1152, "fields": {"name": "New Default Funnel", "sort": 50, "isDefault": "Y"}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.category.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"entityTypeId": 1152, "fields": {"name": "New Default Funnel", "sort": 50, "isDefault": "Y"}, "auth": "**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/crm.category.add
try
{
const response = await $b24.callMethod(
'crm.category.add',
{
entityTypeId: 1152,
fields: {
name: 'New Default Funnel',
sort: 50,
isDefault: 'Y',
},
}
);
const result = response.getData().result;
console.info(result);
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'crm.category.add',
[
'entityTypeId' => 1152,
'fields' => [
'name' => 'New Default Funnel',
'sort' => 50,
'isDefault' => 'Y',
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
// Your logic for processing data
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error adding category: ' . $e->getMessage();
}
BX24.callMethod(
"crm.category.add",
{
entityTypeId: 1152,
fields: {
name: "New Default Funnel",
sort: 50,
isDefault: 'Y',
},
},
(result) =>
{
if (result.error())
{
console.error(result.error());
}
else
{
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'crm.category.add',
[
'entityTypeId' => 1152,
'fields' => [
'name' => "New Default Funnel",
'sort' => 50,
'isDefault' => 'Y',
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": {
"category": {
"id": 5,
"name": "New Default Funnel",
"sort": 50,
"entityTypeId": 1152,
"isDefault": "Y"
}
},
"time": {
"start": 1718116794.208887,
"finish": 1718116794.666272,
"duration": 0.4573848247528076,
"processing": 0.1496260166168213,
"date_start": "2024-06-11T16:39:54+02:00",
"date_finish": "2024-06-11T16:39:54+02:00",
"operating": 0
}
}
Returned Values
|
Name |
Description |
|
result |
Root element of the response. Contains the |
|
time |
Object containing information about the execution time of the request |
Object category
|
Name |
Description |
|
id |
Identifier of the funnel (direction) |
|
name |
Name of the funnel |
|
sort |
Sort index |
|
entityTypeId |
Identifier of the system or user-defined type to which the funnel belongs |
|
isDefault |
Indicates whether the funnel is the default funnel |
|
originId |
Identifier of the data source. Exists only in deals |
|
originatorId |
Identifier of the element in the data source. Exists only in deals |
|
isSystem |
Indicates whether the funnel is a system funnel. Exists only in SPAs |
|
code |
Alias for system funnels. Exists only in SPAs |
Error Handling
HTTP Status: 160, 400
{
"error": "NOT_FOUND",
"error_description": "SPA 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 |
Description |
Value |
|
|
SPA not found |
Occurs with incorrect values for |
|
|
Entity type |
Occurs if the CRM object does not support funnels |
|
|
Adding a system category is prohibited |
Occurs when attempting to create a system funnel in SPAs |
|
|
Access denied |
Occurs if the user does not have sufficient rights to add a funnel |
|
|
Field 'NAME' is required |
Occurs if the required field |
|
|
Default client category does not support updating default state |
Occurs when attempting to create a default funnel for |
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 allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks 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 account administrator has allowed access to this application only for specific users |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Update Sales Funnel crm.category.update
- Get the funnel by Id crm.category.get
- Get the list of Sales Funnels crm.category.list
- Delete Sales Funnel crm.category.delete
- Get Fields of the Sales Funnel crm.category.fields
- How to Create a New Sales Funnel with Stages in a Smart Process