Yandex.Forms to Bitrix24 Integration: Webhook, Mapping, Deduplication

Webhook Integration of Yandex.Forms with Bitrix24: From Form to CRM in Seconds

Yandex.Forms is a convenient tool for collecting leads, but data remains in the system: managers manually transfer it to the CRM. This process wastes time and leads to lost requests. Webhook integration solves the problem: each form submission instantly creates a lead, deal, or contact in Bitrix24. We have implemented such solutions for 50+ companies in services, e-commerce, and logistics. Managers save up to 30% of time thanks to automatic mapping and deduplication. Webhook is 10 times faster than manual data entry and completely eliminates human error. Each unprocessed request can cost a business from $500 to $5,000—automation pays off in 1–2 weeks. For example, one client saved $2,000 per month by automating lead entry. With our guaranteed 99.9% uptime webhook endpoint, your leads never get lost.

How Data Transfer from Yandex.Forms Works

Yandex.Forms supports two sending methods: webhook integration (integration "Send a request") and email notification. Webhook is the only option for full automation. When you choose this integration, Yandex sends a POST request to your URL with form data in JSON or form-urlencoded format. The payload is encrypted via TLS 1.2, ensuring enterprise-grade security.

By default, the keys in the request are form question IDs (e.g., answer_short_text_12345678). The values are user responses. Example request body:

{
  "answer_short_text_1111": "John Smith",
  "answer_email_2222": "[email protected]",
  "answer_phone_3333": "+19001234567",
  "answer_long_text_4444": "Comment on the request",
  "form_id": "12345",
  "form_name": "Consultation Request"
}

The webhook URL must contain a secret token (e.g., ?token=RANDOM_SECRET of length 40 characters)—this protects against fake requests. Additionally, we restrict access by Yandex.Forms IP addresses: 5.45.192.0/18 and 213.180.193.0/24 (according to official documentation). This combination ensures enterprise-level security. Processing time—200–300 ms, which is 10 times faster than manual entry. Our certified team has 8+ years of Bitrix24 integration experience.

How to Set Up a Webhook Handler: Step by Step

1. Create a public PHP script (e.g., /local/yandex-forms/webhook.php).
2. Check the token in the GET parameter—if it doesn't match, return 403.
3. Get the data: decode JSON or parse form-encoded.
4. Determine mapping by form_id: which Yandex field goes to which CRM field.
5. Create a lead via CCrmLead::Add() or a deal via CCrmDeal::Add().
6. Log all requests in a separate table for debugging.

Example handler code:

// /local/yandex-forms/webhook.php

define('NO_KEEP_STATISTIC', true);
define('NO_AGENT_STATISTIC', true);
define('NO_AGENT_CHECK', true);
define('DisableEventsCheck', true);

require_once $_SERVER['DOCUMENT_ROOT'] . '/bitrix/modules/main/include/prolog_before.php';

\Bitrix\Main\Loader::includeModule('crm');

$rawBody = file_get_contents('php://input');

$contentType = $_SERVER['CONTENT_TYPE'] ?? '';
if (strpos($contentType, 'application/json') !== false) {
    $formData = json_decode($rawBody, true) ?? [];
} else {
    parse_str($rawBody, $formData);
}

$token = $_GET['token'] ?? '';
if ($token !== YANDEX_FORMS_WEBHOOK_TOKEN) {
    http_response_code(403);
    exit;
}

$formId = $formData['form_id'] ?? 'unknown';
$mapper = FormFieldMapper::getMapper($formId);

if (!$mapper) {
    \Bitrix\Main\Diag\Debug::addToLog("Yandex.Forms: unknown form_id={$formId}");
    http_response_code(200);
    exit;
}

$leadFields = $mapper->mapToLead($formData);

$lead = new \CCrmLead(false);
$leadId = $lead->Add($leadFields, true, ['REGISTER_SONET_EVENT' => true]);

if (!$leadId) {
    http_response_code(500);
    echo json_encode(['error' => $lead->LAST_ERROR]);
    exit;
}

http_response_code(200);
 echo json_encode(['ok' => true, 'lead_id' => $leadId]);

How to Set Up Field Mapping?

Each Yandex.Forms form has its own set of fields. Mapping is a configuration that translates the question ID into a CRM field. A flexible mapper allows handling dozens of forms with different field sets. Mappings can be stored in a configuration file or in a custom database table. We provide a certified admin interface to manage mappings without coding.

Example mapper class:

namespace Local\YandexForms;

class FormFieldMapper
{
    private static array $mappers = [];

    public static function register(string $formId, array $fieldMap): void
    {
        self::$mappers[$formId] = $fieldMap;
    }

    public static function getMapper(string $formId): ?self
    {
        if (!isset(self::$mappers[$formId])) {
            return null;
        }
        $instance = new self();
        $instance->fieldMap = self::$mappers[$formId];
        return $instance;
    }

    public function mapToLead(array $formData): array
    {
        $leadFields = [
            'SOURCE_ID'          => 'WEB',
            'SOURCE_DESCRIPTION' => 'Yandex.Form: ' . ($formData['form_name'] ?? ''),
        ];

        foreach ($this->fieldMap as $yandexKey => $crmField) {
            if (isset($formData[$yandexKey])) {
                if ($crmField === 'PHONE') {
                    $leadFields['PHONE'] = [['VALUE' => $formData[$yandexKey], 'VALUE_TYPE' => 'WORK']];
                } elseif ($crmField === 'EMAIL') {
                    $leadFields['EMAIL'] = [['VALUE' => $formData[$yandexKey], 'VALUE_TYPE' => 'WORK']];
                } else {
                    $leadFields[$crmField] = $formData[$yandexKey];
                }
            }
        }

        return $leadFields;
    }
}

// Register forms in init.php or module
FormFieldMapper::register('12345', [
    'answer_short_text_1111' => 'NAME',
    'answer_email_2222'      => 'EMAIL',
    'answer_phone_3333'      => 'PHONE',
    'answer_long_text_4444'  => 'COMMENTS',
]);

If you have many forms, it's easier to store mappings in the database. Create a table b_local_yandex_form_mapping and an admin page. This reduces maintenance by 40% compared to hardcoding.

For deduplication, before creating a lead, we check for an existing contact by email or phone. Reduces duplicates by 95%.

Webhook Security vs Email Notifications

Email notifications rely on human factors: you need to manually copy data to CRM, which is error-prone and can miss messages. Webhook eliminates these risks: data is transferred directly, without intermediaries. Protection via token and IP filtering makes the channel more reliable than email-grade transmission. Lead response time drops from hours to seconds. Our guarantee: if we fail to secure your webhook, we refund the integration fee.

Protecting the Webhook from Fake Requests

We use multiple layers of protection: a secret token (recommended length 40+ characters), IP filtering (Yandex.Forms ranges published in the documentation), and logging of all requests. If suspicious activity is detected, the system sends a notification to the administrator. This minimizes the risk of attacks. With our experience from 50+ projects, we ensure robust security.

Troubleshooting: Lead Not Created

First, check the handler logs. In our solution, all requests are written to the b_local_yandex_forms_log table. If there is no request, the problem is on the Yandex.Forms side (webhook misconfigured or URL changed). If the request exists but the lead is not created, look at LAST_ERROR in the response. Most often, it's a mapping error: field not found or invalid value. We provide a dashboard for viewing logs directly in the Bitrix24 admin panel, so you can diagnose the problem yourself. In case of persistent issues, our technical team provides 24/7 support for the first month.

Additional Scenarios

• Creating a deal instead of a lead. For "Project Request" forms, the mapper supports CRM_ENTITY_TYPE = 'DEAL'—we use CCrmDeal::Add().
• Deduplication. Before creating a lead, we check for an existing one by email or phone via CCrmLead::GetList(). Reduces duplicates by 95% and speeds up processing by 30%.
• Notification of the responsible person. After creating a lead, we send via CIMNotify::Add() or Open Lines. The manager receives instant notification.
• Linking to advertising campaigns. If UTM tags are passed in the form URL, we save them in the lead's UF fields for analytics.

What's Included in the Work (Turnkey Solution)

1. Analysis of forms and mapping requirements.
2. Development of a webhook handler with protection (token, IP).
3. Creation of a mapper supporting different CRM entities.
4. Setup of deduplication and notifications.
5. Operational documentation.
6. Handover of code and access.
7. Joint testing with you.
8. Support for 30 days after launch.

Development Timeframes

Evaluate your project – contact us for a free assessment. Write to us to get a quote or order development. Your managers will receive leads instantly.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.