Overview of Events in CRM Activities
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, providing notifications about the creation, updating, and deletion of activities in the CRM timeline.
A detailed explanation of working with events is provided in the article Concept and Benefits of Event Processing.
Quick navigation: all events
How to Receive Events
You can subscribe to activity events through:
- outgoing webhook
- 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.
What the Handler Receives
Activity events pass only the identifier of the activity in the data.FIELDS.ID field. To retrieve the remaining data, call the crm.activity.get method.
The events are triggered for activities of all kinds: system, universal, configurable, and activities of custom types.
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 an activity is created manually or via the crm.activity.add method |
|
|
When an activity is updated manually or via the crm.activity.update method |
|
|
When an activity is deleted manually or via the crm.activity.delete method |