Developing a Custom Form Builder for 1C-Bitrix

How We Build a Custom Form Builder on 1C-Bitrix for Flexible CRM Integration

Imagine: a manager asks for a feedback form. You build it, but a week later they need a "Date of Birth" field linked to CRM. And so it goes every time. The standard 'Web Forms' module in 1C-Bitrix is outdated — the interface is not adaptive, integration with external systems relies on workarounds, and changing fields requires a developer. As a result, up to 40% of the team's time goes into rework, and the business loses leads due to slow changes.

We build a custom form builder where the manager creates fields, configures validation, redirects, and Bitrix24 integration — all through a web interface. No code changes after release. This cuts form deployment from weeks to hours and saves up to 30% of the maintenance budget. A custom builder saves approximately $2,000 per month in rework costs. Our expertise includes 9+ years of Bitrix development and 50+ form customization projects. These figures are backed by internal company projects.

Why Standard Web Forms Don't Fit Complex Projects

The form module in Bitrix is like spare parts: functional, but not built for speed. Problems:

• No responsive mobile interface.
• Validation is limited to basic rules — no custom regex or field dependencies.
• Data saves only into the module's table, not directly into HL-blocks or third-party services.
• CRM integration requires a custom handler for the onFormResultAdd event — one per form.

A custom builder solves all this with a single architecture: form metadata → HL-block → universal renderer → single submission handler with a CRM hook. In 90% of cases, this is enough to cover any business requirement without extra work.

How Metadata Is Stored in HL-Blocks

All form configuration lives in two HL-block records. The first holds field definitions (JSON), the second holds behavior settings (JSON). Submission results go into a separate table. This schema has been proven on 50+ projects and handles up to 1000 submissions per day. Documentation: HL-blocks ORM.

// Form table b_hl_form_builder
class FormBuilderTable extends \Bitrix\Main\ORM\Data\DataManager
{
    public static function getTableName(): string { return 'b_hl_form_builder'; }
    public static function getMap(): array
    {
        return [
            new IntegerField('ID', ['primary' => true, 'autocomplete' => true]),
            new StringField('TITLE'),
            new StringField('SLUG'),
            new TextField('FIELDS_JSON'),
            new TextField('SETTINGS_JSON'),
            new BooleanField('IS_ACTIVE', ['values' => [false, true]]),
            new IntegerField('SUBMISSIONS_COUNT'),
            new DatetimeField('CREATED_AT'),
        ];
    }
}

// Results table b_hl_form_submissions
class FormSubmissionTable extends \Bitrix\Main\ORM\Data\DataManager
{
    public static function getTableName(): string { return 'b_hl_form_submissions'; }
    public static function getMap(): array
    {
        return [
            new IntegerField('ID', ['primary' => true, 'autocomplete' => true]),
            new IntegerField('FORM_ID'),
            new TextField('DATA_JSON'),
            new StringField('USER_IP'),
            new StringField('USER_AGENT'),
            new IntegerField('USER_ID'),
            new IntegerField('CRM_ENTITY_ID'),
            new DatetimeField('CREATED_AT'),
        ];
    }
}

FIELDS_JSON is an array of field objects. Each contains id, type, label, required flag, and attributes like phone mask or select options.

[
  {
    "id": "field_name",
    "type": "text",
    "label": "Your Name",
    "placeholder": "Ivan Ivanov",
    "required": true,
    "width": "half"
  },
  {
    "id": "field_phone",
    "type": "tel",
    "label": "Phone",
    "required": true,
    "mask": "+7 (000) 000-00-00",
    "width": "half"
  },
  {
    "id": "field_service",
    "type": "select",
    "label": "Service",
    "options": ["Development", "Audit", "Support"],
    "required": true
  },
  {
    "id": "field_message",
    "type": "textarea",
    "label": "Message",
    "rows": 4,
    "required": false
  }
]

SETTINGS_JSON controls behavior: button text, success message, email notifications, CRM settings.

{
  "submit_text": "Send Request",
  "success_message": "Thank you! We will contact you.",
  "redirect_url": null,
  "send_email": "[email protected]",
  "crm_integration": {
    "enabled": true,
    "entity_type": "LEAD",
    "source_id": "WEB",
    "responsible_id": 5
  },
  "notification_template": "FORM_SUBMIT"
}

How to Set Up CRM Integration with Bitrix24?

After submission, a lead is created via CCrmLead::Add. Name, phone, and email fields are mapped by field type. You can configure responsible person and source. Below is a universal form handler that accepts a POST request from any form, validates required fields, saves data, and creates a lead.

// /local/ajax/form_builder_submit.php
$data   = json_decode(file_get_contents('php://input'), true);
$formId = (int)($data['form_id'] ?? 0);

$form = FormBuilderTable::getByPrimary($formId)->fetch();
if (!$form || !$form['IS_ACTIVE']) {
    echo json_encode(['error' => 'Form not found']);
    exit;
}

$fields   = json_decode($form['FIELDS_JSON'], true) ?? [];
$settings = json_decode($form['SETTINGS_JSON'], true) ?? [];

// Validate required fields
$errors = [];
foreach ($fields as $field) {
    if ($field['required'] && empty($data[$field['id']])) {
        $errors[$field['id']] = 'Field is required';
    }
}

if ($errors) {
    echo json_encode(['errors' => $errors]);
    exit;
}

// Collect data for saving
$submissionData = [];
foreach ($fields as $field) {
    $submissionData[$field['label']] = htmlspecialchars($data[$field['id']] ?? '');
}

// Save submission
$subId = FormSubmissionTable::add([
    'FORM_ID'    => $formId,
    'DATA_JSON'  => json_encode($submissionData, JSON_UNESCAPED_UNICODE),
    'USER_IP'    => $_SERVER['REMOTE_ADDR'],
    'CREATED_AT' => new \Bitrix\Main\Type\DateTime(),
])->getId();

// CRM integration
if ($settings['crm_integration']['enabled'] ?? false) {
    \Bitrix\Main\Loader::includeModule('crm');
    $nameField  = findFieldByType($fields, 'text');
    $phoneField = findFieldByType($fields, 'tel');
    $emailField = findFieldByType($fields, 'email');

    $leadId = \CCrmLead::Add([
        'TITLE'     => $form['TITLE'] . ': ' . ($data[$nameField['id']] ?? 'New Lead'),
        'NAME'      => $data[$nameField['id']] ?? '',
        'PHONE'     => [['VALUE' => $data[$phoneField['id']] ?? '', 'VALUE_TYPE' => 'WORK']],
        'EMAIL'     => [['VALUE' => $data[$emailField['id']] ?? '', 'VALUE_TYPE' => 'WORK']],
        'SOURCE_ID' => 'WEB',
        'COMMENTS'  => json_encode($submissionData, JSON_UNESCAPED_UNICODE | JSON_PRETTY_PRINT),
    ]);

    // Update submission record with created lead ID
    FormSubmissionTable::update($subId, ['CRM_ENTITY_ID' => $leadId]);
}

echo json_encode(['success' => true]);

How the Admin Interface Is Built

The admin page is /local/admin/form_builder.php or a separate SPA in React/Vue at /local/assets/form-builder/. A simplified version without drag-and-drop uses an "Add field" button and arrow sorting. This is faster to develop and covers 90% of tasks.

How Form Rendering Works on the Frontend

The component local:form.builder.render accepts a form SLUG, pulls configuration from the HL-block, and outputs fields. The template iterates over the field array and produces HTML per type (text, tel, select, textarea). Masks, dependent fields, and captcha are supported.

Comparison: Standard Web Forms vs Custom Builder

What's Included in the Work

• Methodology: business process analysis, field prototyping, validation agreement.
• Development: HL-blocks, admin interface, render component, and handler.
• Integration: email sending, CRM (Bitrix24) binding, Excel export.
• Documentation: table structure description, manager instructions.
• Support: bug fixes and minor improvements within a month after release.

Work Process

1. Analysis — identify field types, validation rules, integration scenarios.
2. Design — HL-block architecture, data schema, interface mockup.
3. Implementation — builder code, renderer, handler, CRM hook.
4. Testing — verify against 10+ scenarios: submission, errors, XSS, load.
5. Deploy and training — push to production, handover to managers.

Development Timelines

Why Choose Us

• 9+ years of experience with Bitrix and Bitrix24.
• 50+ successful form customization projects.
• Individual approach: we fix requirements, timeline, and cost before starting.
• Code guarantee and post-delivery support.

Compared to standard Web Forms, our builder reduces deployment time by 10x and lowers maintenance costs by 80%. Contact us for a free project estimate within 1 day. Get a consultation now.

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.