Depesher Notifications

What this solution does

The Depesher Notifications module sends events from your website or online store to the Depesher service. This solution helps track orders, requests, content changes, and other events from a unified notification center.

The module is free. The usage right is provided without limits on the number of installations and without a fixed expiration date, valid for the entire term of the exclusive right. Use is permitted on both personal and commercial sites.

In the Bitrix administrative section, you select events, group them, and set rules for sending to Depesher channels. Events are placed in a local queue, and sending is performed by a separate handler. In case of temporary network errors or service errors, the module automatically retries requests.

Supported events:

User self-registration and failed login attempts.

Adding, editing, and deleting elements in selected information blocks.

Creating an order, changing its status, as well as canceling and restoring an order.

Full payment of an order and cancellation of full payment.

Creation of a result in a selected web form.

Completion of catalog import from 1C.

The module allows developers to register and send custom events via the PHP API. The availability of built-in events depends on the installed edition and the presence of corresponding Bitrix modules.

Features include multiple notification channels with separate sending rules for each channel. Rules can be defined for individual events or groups of events. Filtering is performed based on event-specific parameters: websites, information blocks, web forms, and order statuses.

The system supports multi-site configuration where rules can account for the site identifier. A test send function is available to verify channel connectivity. The delivery log records event data, sending status, and attempt history. Failed deliveries can be manually retried while they remain in the log and within their validity period.

The queue status page displays a counter of notifications rejected due to queue overflow. Access rights are separated between viewing and managing the module. The system transmits the source name and environment to distinguish between production, testing, and development websites.

The module sends event data to the external Depesher service via a webhook. Operation requires a pre-created channel in Depesher and a webhook address pointing to the host depesher.ru in the subdirectory w with the identifier public_id. Recipient configuration and notification display settings must be performed directly within the Depesher service interface. Support for arbitrary addresses of third-party services is not provided.

The module and the Depesher service are available free of charge. Currently, only a free tariff exists in the service; paid options are not available. Connecting and using this integration does not require additional payments.

Requirements and limitations

The hosting must support regular execution of Bitrix agents via cron at one-minute intervals. Executing agents on page visits must be disabled to prevent delays in website loading.

The website server requires outgoing HTTPS access to the host depesher.ru on port 443.

The task queue and event log are stored in the website database. Support is provided for MySQL with the InnoDB engine and PostgreSQL.

The installer requires PHP version 8.2 or newer and the main module version 20.0.0 or newer. Functionality has been tested on PHP 8.2, 8.4, and main module version 26.150.0.

Full support is provided for UTF-8 and Windows-1251 character encodings.

Installation and basic configuration require Bitrix administrator privileges. Setting up cron tasks requires access to the hosting control panel or assistance from a server administrator. Integrating custom events requires PHP development skills.

No additional third-party modules are required for the core functionality. However, specific built-in events require corresponding standard Bitrix modules to function correctly.

The active delivery queue is limited to 10,000 items. A single event sent to multiple channels generates multiple separate deliveries. If the queue limit is reached, new events are rejected entirely.

The delivery validity period is 48 hours from the moment the item is added to the queue. Once this period expires, the notification is not sent and cannot be manually retried.

Automatic sending stops after 10 failed attempts or upon expiration of the validity period.

Completed history is stored only for the current day according to the site server's time zone. Old completed records are deleted by the cleanup agent; the log is not intended for long-term archival storage.

The status SENT indicates that the Depesher system has accepted the request. Confirmation of delivery to the final recipient must be verified within the Depesher interface. Duplicate notifications may occur if the same request is submitted multiple times.

The Depesher Notifications module tracks the standard completion of the catalog import process.

Data transmitted

The module sends the event code, timestamp, installation ID, site ID (if present), source name, environment, and specific event data. Built-in handlers transmit object IDs and relevant change details; infoblock events also include the element name, symbolic code, and activity status. The HTTP header carries the module version, platform version, and the Bitrix edition defined by the module.

Built-in handlers do not transmit user logins, names, surnames, email addresses, or phone numbers, order properties, web form responses, passwords, cookies, session contents, or Bitrix license keys. Do not place personal data in infoblock element names, source signatures, or other transmitted fields. The data composition for custom PHP events is determined by the integration developer.

If “Depesher Notifications” is required, General iT can help with installation, configuration and a technical check after integration.