Bitrix24

Overview

Signals writes leads captured on an ad platform or a form straight into Bitrix24, so they reach your pipeline without an export step.

Signals maps each lead form field to a Bitrix24 field and creates the record in the Leads section. The lead arrives with the platform lead ID attached, which is what lets you tie a Bitrix24 record back to the ad that produced it.

Unlike the other CRM destinations, Bitrix24 is connected with a webhook URL that you generate inside Bitrix24 yourself. There is no sign-in step.

Supported sources

Sources supported by Bitrix24

Category	Supported
Lead generation	Google Forms LinkedIn Lead Generation Forms Meta Lead Ads Snapchat Lead Generation Ads TikTok Lead Ads

Prerequisites

Before connecting Bitrix24, make sure you have:

• A Bitrix24 account with permission to create webhooks. This usually means an administrator.
• An inbound webhook carrying the crm.lead.list method, which is what the connection URL is generated from.
• A field in the Leads section to hold the lead ID from your source. Create it before you start.
• A Datahash Studio account with the target project selected.
• A lead generation source already connected in the same project.

Authentication

In Studio, open Destinations, find the CRM category, and click the Bitrix24 tile. This connector authenticates with a single REST API URL generated from a Bitrix24 webhook.

1. Paste the Bitrix24 REST API URL.
2. Click Next.

Generating the URL in Bitrix24, if you do not already have a webhook:

1. Open Menu, then CRM.
2. Under Add-ons, click Rest API.
3. Click Import & Export Data, then Import Customers.
4. In the request builder, add the crm.lead.list method.
5. Copy the generated REST API URL, then click Save.

If you already have a webhook, open the Integrations section, open the existing integration, add the crm.lead.list method in the request builder, copy the URL and save.

Caution

The URL contains an authorization code, so treat it as a credential. Anyone holding it can write into your CRM. Paste it on the Datahash connection screen only, and revoke the webhook in Bitrix24 if it has been shared.

Configuration

Source and connection

1. Choose the source type, which is the lead platform or form the leads come from.
2. Select the connection name created when that source was set up.
3. Give this destination connection a name.

Leads are written to the Leads section, which is what the crm.lead.list method in the webhook determines. There is no separate selection step in Studio.

Field mapping

The mapping screen puts your lead form fields on the left and the Bitrix24 schema fields on the right.

Two rules apply to every mapping on this connector.

• The lead ID from your source must be mapped. It is named after the platform the lead came from, for example Meta Lead ID or TikTok Lead ID, and it is the only field that has no substitute.
• Every field your CRM marks as required, shown with an asterisk in the mapping screen, must be mapped as well. An unmapped required field fails the record rather than the connection, so the setup will look healthy while leads quietly do not arrive.

Map as many further fields as you need. Anything you leave unmapped is simply not written.

Test connection and response preview

Click Test Connection before finishing. This sends a sample record into Bitrix24, so the test lead lands in your live CRM and someone will need to remove it afterwards. Once the test passes, click Finish.

Manage instance

To add another, open Manage Connections and click Add Instance, then work through the same steps. A CRM can hold several instances, so one connection per lead source is a reasonable pattern where the mapping differs between them.

To change one, click the connection name in Manage Connections, then the edit icon in the top right. Update the fields, click Test Connection and then Finish. Clicking Cancel keeps the previous configuration running; updates apply only after you finish.

Data & identifiers

Lead data is written into your own CRM, so nothing is hashed on the way. What arrives is what the lead form captured, in plain text, which means the CRM’s own access controls and retention rules are what govern it from that point on.

There is no fixed field specification for this destination. The fields available to map are whatever your lead form captured on one side and whatever your CRM schema exposes on the other, so the shape differs from one connection to the next.

Best practices

• Generate the webhook against an account that will not be deactivated. If the creating user is removed, the URL stops working.
• Add only the crm.lead.list method the connection needs rather than granting the webhook broader scope.
• Store the URL as a secret. It is the whole credential, and it is not masked once pasted.
• Create the lead ID field in the Leads section before you begin.
• Map every field marked with an asterisk. Records missing one are rejected without the connection changing state.
• Remove the test lead after Test Connection passes. It is a real record in your live account.

Troubleshooting & FAQ

The URL is rejected. Check the crm.lead.list method was added before the webhook was saved, and that the URL was copied in full including the authorization code.

Leads are not arriving. Confirm the source is connected in the same project and receiving leads, and that the connection was finished rather than left open.

Delivery stopped suddenly. The webhook may have been deleted, or the user who created it deactivated. Generate a new webhook and update the connection.

Some leads arrive and others do not. The ones failing are missing a value for a Bitrix24 required field.

A test lead is sitting in Bitrix24. That is the sample sent by Test Connection. Delete it manually.

Can I reuse one webhook for several connections? You can, but a separate webhook per connection is easier to revoke without disrupting anything else.