Overview of Events When Working with Open Channels
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 almost in real-time: receiving notifications about the creation, updating, or deletion of messages in the open channel chat.
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 open channel events through the application and the event.bind method.
An example of a handler for the event is described in the article How to Test Your Handler for Processing Events in Bitrix24.
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:
imopenlinesWho can subscribe: any user
|
Event |
Triggered |
|
When creating an Open Channel session manually or using the imopenlines.session.start method |
|
|
When a message is added to the chat manually or by the method imopenlines.crm.message.add |
|
|
When a message in the chat is modified manually |
|
|
When a message in the chat is deleted manually |
|
|
When closing an Open Channel session manually |