1C-Bitrix Web Form to Bitrix24 CRM Integration

1C-Bitrix Web Form to Bitrix24 CRM Integration

We often encounter a recurring challenge: a website has a well-configured feedback form, but managers operate within Bitrix24 CRM, and leads are received via email without structured data. Data is not synchronized, the sales funnel is incomplete, and analytics are absent. For example, a prospect submits a web form, but the manager learns about it an hour later—the lead becomes cold. Without automatic data sync, every call or application becomes manual work, while competitors already have CRM automation. Estimates indicate that lead loss can reach 30% without integration. The typical integration cost is $500–1000, offering a return on investment within 3 months through reduced manual labor and increased conversion.

The standard Bitrix web form modules (bitrix:main.feedback, bitrix:form.result.new) store results in the b_form_result table and send email notifications. Without CRM integration, data remains in the site database—managers do not see them in Bitrix24, and communication history is lost. According to the official 1C-Bitrix documentation, the OnAfterResultAdd event of the form module allows intercepting result data before notification is sent.

Why Native Web Forms Are Better Than CRM Forms

Bitrix24 CRM forms are easier to set up, but their hosting on a third-party domain (b24-cdn.bitrix24.by) negatively impacts SEO and page load speed. Moreover, you cannot customize their appearance to match the site design without an iframe wrapper. A native web form stays on your own domain, passes all UTM tags and cookies, and the styles are fully controlled by the site template. According to our experience, the conversion rate of such forms is 20–30% higher.

How to Set Up Integration: 6 Steps

1. Audit current forms and CRM—determine which forms send data and which fields are needed in CRM.
2. Create the handler—subscribe to the OnAfterResultAdd event in init.php.
3. Field mapping—set up correspondence between form fields and lead fields in a configuration array.
4. Create custom fields—via REST API crm.userfield.add for non-standard data.
5. Deduplication—check existing leads by email/phone before creating a new one.
6. Testing and deployment—verify data transfer, files, and business processes.

Web Form Result Handler

Bitrix provides the OnAfterResultAdd event of the form module. Subscribe in init.php:

AddEventHandler('form', 'OnAfterResultAdd', function($formId, $resultId, $fields) {
    // Only for needed forms
    $targetForms = [3, 7, 12]; // Form IDs: callback, consultation, partnership
    if (!in_array($formId, $targetForms)) return;

    $answers = CFormResult::GetDataByID($resultId, [], $arrResult);
    $mapped  = mapFormAnswers($formId, $answers);

    $b24 = new B24Sender(getenv('B24_WEBHOOK_URL'));
    $b24->sendLead($mapped);
});

Mapping Form Fields to Lead Fields

Web form fields are stored in b_form_field, answers in b_form_result_answer. Linked by FIELD_ID. Mapping is configured in a config:

$formMapping = [
    3 => [ // Form "Callback Request"
        'q_name'    => 'NAME',
        'q_phone'   => 'PHONE',
        'q_comment' => 'COMMENTS',
        'utm_source'=> 'UTM_SOURCE',
    ],
    7 => [ // Form "Partnership"
        'q_company'   => 'COMPANY_TITLE',
        'q_contact'   => 'NAME',
        'q_email'     => 'EMAIL',
        'q_direction' => 'COMMENTS',
    ],
];

Case Study: Multi-Step Application Form

From our practice—an IT integrator website with a project application form: 4 steps (project type, budget, timeline, contacts). The standard web form module stores all answers in b_form_result_answer. The task: create a qualified lead in Bitrix24 with filled fields and correct funnel.

Solution: steps 1–3 are saved in session, step 4 submits the complete form. In the OnAfterResultAdd handler, we collect all fields and create a lead with custom CRM fields:

$leadFields = [
    'TITLE'       => 'Project: ' . $answers['project_type'],
    'OPPORTUNITY' => $answers['budget_from'], // budget as lead amount
    'CURRENCY_ID' => 'RUB',
    'UF_CRM_PROJECT_TYPE'   => $answers['project_type'],
    'UF_CRM_DEADLINE_WEEKS' => $answers['deadline'],
    // UF_CRM_* — custom lead fields in Bitrix24
];

Custom fields (UF_CRM_*) are created in Bitrix24 via crm.userfield.add beforehand. After lead creation, we automatically start a business process in Bitrix24 via bizproc.workflow.start. This guarantees no application gets lost.

How to Transfer Files from Forms to CRM?

If a form includes a file upload field (technical specification, brief), the file must be transferred to Bitrix24. REST API crm.lead.add does not support binary upload directly—we use disk.folder.uploadfile to upload to Bitrix24 Drive, then attach to the lead via crm.activity.add with type DOCUMENT. The file appears in the lead card, and the manager sees the attachment immediately.

Lead Deduplication

The same company often fills out the form multiple times. We check by email and phone before creating:

$existing = $b24->call('crm.duplicate.findByComm', [
    'type'   => 'EMAIL',
    'values' => [$email],
    'entity_type' => 'LEAD',
]);

if (!empty($existing['result']['LEAD'])) {
    // Add activity to existing lead, do not create new
    $b24->call('crm.activity.add', [...]]);
}

What's Included in the Service

Average cost: $800 per form, with discounts for multiple forms. Our team has 7 years of expertise in Bitrix integration and has successfully completed over 60 projects, ensuring reliable and efficient data flow.

All work is performed with a guarantee—we take responsibility for the stability of integration and uninterrupted data transfer. The integration typically pays for itself within 3 months. Managers save up to 2 hours daily. If you have any questions, contact us—we'll assess the project within one day and offer the optimal solution. Order integration with quality guarantee.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.