Skip to content

Bitrix24 ​

The Bitrix24 connection pulls users, companies and deals from your portal through an inbound webhook. The system works on top of Bitrix24: data is loaded for review and lands in the CRM only after you confirm it. Bitrix24 keeps working as before.

Connection status — Beta. No platform keys are needed: you create the webhook in your own portal.

How to connect ​

  1. In Bitrix24 open Developer resources → Other → Inbound webhook.
  2. Select the CRM (crm) and Users (user) permissions and save. Copy the URL, e.g. https://company.bitrix24.com/rest/1/xxxxxxxx/.
  3. In the system open Connectors (/connectors) → Bitrix24 card.
  4. Paste the URL into Inbound webhook URL and click Connect Bitrix24. The system checks right away that the webhook works.

The webhook URL is an access key. It is stored encrypted and never shown again after connecting. To change it, paste a new URL and click Replace webhook.

Only the organization owner or an administrator can connect and disconnect.

Changes from Bitrix24 (optional) ​

To receive changes automatically, without a manual pull:

  1. Copy the Handler URL from the Bitrix24 card.
  2. In Bitrix24 create an Outbound webhook with this URL and these events: company add/update/delete, deal add/update/delete, user add.
  3. Copy the issued Application token, paste it on the card and click Save token.

Until the token is saved, events from Bitrix24 are not accepted.

How to pull data ​

  1. Click Pull from Bitrix24. Users are loaded first, then companies, then deals.
  2. Large portals are loaded in parts — click again to continue. Next pulls take only changed companies and deals.
  3. Outbound webhook events land in the same review list.

Review and confirm ​

The Import review block lists the pulled records: type (user, company, deal), name and deal amount.

  • Confirm selected or Confirm all on this page — creates or updates CRM records.
  • Skip selected — the record never reaches the CRM.
In Bitrix24In the system
UserLinked to the organization member with the same e-mail. No accounts are created; without a matching member the record stays in review
CompanyClient (company)
DealLead linked to the client. Manager — the linked user. Deal amount and currency are put in the note

Repeated pulls do not create duplicates: every Bitrix24 record is linked to a record in the system. If a record changes after confirmation, it shows up for review again marked “update”. Deletions in Bitrix24 never delete anything in the system.

Invoices are never created from deals automatically.

Disconnecting ​

Disconnect removes the stored webhook and token. Already confirmed clients and leads stay. Delete the webhook itself in your portal.

Security ​

  • The webhook URL and the application token are stored encrypted only.
  • Requests to Bitrix24 are rate limited (at most 2 per second); when the limit is hit the request is retried after a pause.
  • An event is accepted only at the secret handler URL, with the correct application token and only from the connected portal; re-delivery creates no duplicates.
  • Connecting, pulls, disconnecting and every created record are written to the audit log without keys or tokens.

Errors ​

The last error is shown on the card. “bitrix_webhook_unauthorized” means the webhook was deleted or lacks permissions: create a new one and click Replace webhook.

See also: Finance integrations.

AIDIR client documentation · docs.aidir.kz