Overview of Events When Working with Contacts

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 almost real-time: receiving notifications about the creation, updating, or deletion of contacts.

In all three events, the handler receives only the contact identifier in data.FIELDS.ID, without the field values. After a contact is created or updated, request its data with the method crm.contact.get or crm.item.get with entityTypeId = 3. After deletion, the contact is no longer available, so retain the data you need on your side in advance.

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 contact events through:

outgoing webhook
application and the method event.bind

An example of a handler 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.