Event for updating a custom type CRM object onCrmDynamicItemUpdate
Scope:
crmWho can subscribe:
any user
The event triggers when an element of any custom object type in CRM is modified.
Events will not be sent to the application until the installation is complete. Check the application installation
What the handler receives
Data is transmitted as a POST request
Event for changing an element with id = 24, belonging to a smart process with entityTypeId = 1220:
{
"event": "ONCRMDYNAMICITEMUPDATE",
"event_handler_id": "5",
"data": {
"FIELDS": {
"ID": "24",
"ENTITY_TYPE_ID": "1220"
}
},
"ts": "1723538517",
"auth": {
"access_token": "s6p6eclrvim6da22ft9ch94ekreb52lv",
"expires_in": "3600",
"scope": "crm",
"domain": "some-domain.bitrix24.com",
"server_endpoint": "https://oauth.bitrix.info/rest/",
"status": "F",
"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 custom type CRM object. Contains a single key |
|
data.FIELDS |
Object containing information about the fields of the modified custom type CRM object. The structure is described below |
|
ts |
Date and time the event was sent from the event queue |
|
auth |
Object containing authorization parameters and information about the account where the event occurred. The structure is described below |
Parameter FIELDS
|
Parameter |
Description |
|
ID |
Identifier of the modified custom type CRM object |
|
ENTITY_TYPE_ID |
Identifier of the custom CRM type |
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.
Events of system object types
Although universal CRM methods allow adding and modifying objects of standard types such as deals, leads, contacts, companies, and estimates, the event onCrmDynamicItemUpdate will not trigger when modifying the listed objects.
To track changes to deals, leads, etc., you can use specific events:
- Event on deal update onCrmDealUpdate
- Event onCrmLeadUpdate
- Event onCrmContactUpdate
- Event on Company Update onCrmCompanyUpdate
- Event on updating the estimate onCrmQuoteUpdate
When new invoices are modified, the event onCrmDynamicItemUpdate will trigger.
Continue exploring
- Event Handler
- Register a new event handler event.bind
- Overview of CRM Object Events
- Event for Creating a Custom Type CRM Object onCrmDynamicItemAdd
- Event for Deleting a Custom CRM Object onCrmDynamicItemDelete