Overview of Events When Working with Smart Process Elements

If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.

Events allow applications to respond to changes in near real-time: receiving notifications about the creation, updating, or deletion of smart process elements.

Detailed information on working with events is described in the article Concept and Benefits of Event Processing.

Quick navigation: all events

How to Receive Events

You can subscribe to events of smart process elements through:

outgoing webhook
application and the method event.bind

An example of a handler code for an event is described in the article How to Test Your Handler for Processing Bitrix24 Events.

How to Choose Which Events to Receive

There are two ways to receive smart process events: subscribe to basic events for all smart processes or to the event of a specific smart process.

Basic Event for All Smart Processes. If the handler needs to receive events for elements of all smart processes, subscribe to the events:

onCrmDynamicItemAdd — creation of a smart process element
onCrmDynamicItemUpdate — updating of a smart process element
onCrmDynamicItemDelete — deletion of a smart process element

The basic event triggers for elements of different smart processes. The handler receives the data.FIELDS object:

ID — identifier of the smart process element
ENTITY_TYPE_ID — identifier of the smart process to which the element belongs

To process events of the desired smart process, check the value of data.FIELDS.ENTITY_TYPE_ID. The entityTypeId of the smart process can be obtained using the method crm.type.list.

Event for a Single Smart Process. If the handler needs to receive events for only a specific smart process, use the event with the suffix _{entityTypeId}. This suffix indicates which smart process the event relates to.

For example, for a smart process with entityTypeId = 147, the event for creating an element will be called ONCRMDYNAMICITEMADD_147.

Before subscribing, check if such an event is available:

for the application — using the method events
for the outgoing webhook — in the outgoing webhook builder

If the event with the suffix is not available, subscribe to the basic event onCrmDynamicItemAdd, onCrmDynamicItemUpdate, or onCrmDynamicItemDelete. In the handler, check the data.FIELDS.ENTITY_TYPE_ID field: it contains the entityTypeId of the smart process to which the element belongs.

Server Availability for Sending and Receiving Events

The event handler server must be accessible from the outside. To configure the accessibility of the event handler server and application, refer to the article Required network access.

For cloud Bitrix24, no additional configuration is required. For on-premise Bitrix24, configure accessibility on the server or hosting according to the article Required network access.