Overview of Events in CRM Activities
Events allow applications to respond to changes in near real-time, providing notifications about the creation, updating, and deletion of deals in the CRM timeline.
A detailed explanation of working with events is provided in the article Concept and Benefits of Event Processing.
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.
Quick navigation: all events
How to Receive Events
You can subscribe to deal events through the application and the event.bind method.
An example of a handler code for the event is described in the article How to Test Your Handler for Processing Bitrix24 Events.
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.
Overview of Events
Scope:
crmWho can subscribe: any user
|
Event |
Triggered |
|
When a deal is created manually or via the crm.activity.add method |
|
|
When a deal is updated manually or via the crm.activity.update method |
|
|
When a deal is deleted manually or via the crm.activity.delete method |