Event on changing the deal's Sales Funnel onCrmDealMoveToCategory
Scope:
crmWho can subscribe: any user
The event ONCRMDEALMOVETOCATEGORY will trigger when the deal's Sales Funnel changes.
Currently, you can only subscribe to the event from the application.
What the handler receives
Data is transmitted as a POST request
{
"event": "ONCRMDEALMOVETOCATEGORY",
"event_handler_id": "655",
"data": {
"FIELDS": {
"ID": "6675",
"CATEGORY_ID": "1",
"STAGE_ID": "C1:NEW"
}
},
"ts": "1736424182",
"auth": {
"access_token": "s6p6eclrvim6da22ft9ch94ekreb52lv",
"expires_in": "3600",
"scope": "crm",
"domain": "some-domain.bitrix24.com",
"server_endpoint": "https://oauth.bitrix.info/rest/",
"status": "L",
"client_endpoint": "https://some-domain.bitrix24.com/rest/",
"member_id": "a223c6b3710f85df22e9377d6c4f7553",
"refresh_token": "4s386p3q0tr8dy89xvmt96234v3dljg8",
"application_token": "51856fefc120afa4b628cc82d3935cce"
}
}
|
Parameter |
Description |
|
event |
Symbolic event code. In this case — |
|
event_handler_id |
Identifier of the event handler |
|
data |
Object containing information about the modified deal. Contains a single key |
|
data.FIELDS |
Object containing information about the fields of the modified deal. The structure is described below |
|
ts |
Date and time the event was sent from the event queue |
|
auth |
Object containing authorization parameters and data about the account where the event occurred. The structure is described below |
Parameter FIELDS
|
Parameter |
Description |
|
ID |
Identifier of the modified deal |
|
CATEGORY_ID |
Identifier of the new Sales Funnel |
|
STAGE_ID |
Identifier of the new deal stage |
Parameter auth
Required parameters are marked with *
|
Name |
Description |
|
access_token |
Authorization token OAuth 2.0 |
|
expires_in |
Time in seconds until the token expires |
|
scope* |
Scope under which the event occurred |
|
domain* |
Address of Bitrix24 where the event occurred |
|
server_endpoint* |
Address of the Bitrix24 authorization server needed to refresh OAuth 2.0 tokens |
|
status* |
Status of the application that subscribed to this event:
|
|
client_endpoint* |
Common path for REST API method calls for Bitrix24 where the event occurred |
|
member_id* |
Identifier of Bitrix24 where the event occurred |
|
refresh_token |
Token for extending authorization OAuth 2.0 |
|
application_token* |
Token for secure event handling |
Authorization tokens are not always passed to the event handler. If the hit that initiated the event could not be linked to a specific Bitrix24 user, the tokens are not passed. Always check the contents of the auth key in the code.
It is recommended to store tokens obtained earlier during the application installation. Use them when working with the application interface in the form of embeds, widgets, and so on.
Continue exploring
- Event Handler
- Register a new event handler event.bind
- Event when creating a deal onCrmDealAdd
- Event on deal update onCrmDealUpdate
- Event on deal deletion onCrmDealDelete