Turnkey Low-Code Automation on Bitrix24

Your budget for custom development has run out, but processes are still manual. In-house developers are busy, and Bitrix24's low-code tools—robots, smart processes, and business processes—remain unconfigured. We've seen companies that purchased licenses but ended up with automation chaos: conflicting robots, stuck processes, unsynchronized stages. We configure low-code turnkey on Bitrix24: from audit to testing—without unnecessary code and with stability guaranteed. Our team has substantial experience in Bitrix24 low-code automation, having completed 50+ projects over 6 years.

How to set up smart processes for typical scenarios?

Smart processes are custom CRM entities with their own stages, fields, and automation. They allow creating a business object without writing PHP. Typical uses: contract approval, complaint handling, equipment tracking. Smart processes are 5x faster to set up than custom PHP modules. Using low-code robots reduces development time by 70% compared to traditional scripting.

Configuration includes five steps:

1. Create the entity: CRM → Settings → Smart Processes → Create. Set the name and link to a funnel.
2. Stages: define the sequence—draft, pending approval, approved, rejected.
3. Fields: types—string, number, date, link to user or CRM entity.
4. Access rights: roles—administrator, manager, head.
5. Automation: robots and triggers on stage change.

Smart processes are available on Professional and Enterprise plans. Basic smart process configuration starts at $500; complex business processes from $1500. Experience shows that configuring one smart process takes 2-4 hours.

Why do CRM robots conflict and how to avoid it?

Robots are actions performed automatically upon stage change. There are dozens of built-in actions: email, task, field, timer, webhook. Conflicts occur when multiple robots try to modify the same field simultaneously or run on the same stage without considering order.

We've developed three rules that save hours of debugging:

• One robot, one action. Don't mix email and field changes in one robot. A chain of three robots is easier to read than one robot with five actions.
• Conditions before action. Use a conditional robot (condition) before execution, not inside each action.
• Pass variables explicitly. The result of one robot (created task ID) is passed to the next via {{ID}}. Document the chain.

Timeouts are another cause of failures. The "Wait" robot pauses the chain. If the stage changes during the wait, subsequent robots won't execute. Check logs in Automation → Robots.

For example, on one project, a client had three robots that all tried to update the "Status" field when a deal moved to "Won". This caused intermittent errors. We consolidated them into a single conditional robot that performed checks, reducing error rate to zero.

When are business processes more effective than robots?

Business processes (BPs) are more powerful: branching, loops, parallel flows, custom activities. They are ideal for multi-level approvals (manager → legal → director) and processes with conditions (if amount > 100,000 — additional approval).

BPs can be launched on CRM entities, list items, documents. They are also supported for smart processes. The choice between robots and BPs is a balance of setup speed and flexibility. For simple chains, robots suffice; for multi-stage approvals, use BPs.

What's included in turnkey low-code configuration

• Audit of current automation: identifying conflicting robots and duplicates.
• Designing smart processes for business scenarios.
• Configuring CRM robot chains with documented logic.
• Configuring business processes with branching and approvals.
• Connecting external services via webhooks (e.g., REST API).
• Testing scenarios: running an element through all stages with each robot verified.
• Documentation and training: transferring rights to administrators.

Official Bitrix24 documentation confirms that low-code automation reduces developer workload by 60%.

Our proven process for low-code configuration

We follow a structured approach to ensure reliability and maintainability:

1. Discovery: Analyze existing manual processes and identify automation candidates.
2. Design: Map out smart processes, robot chains, and business process flows using visual diagrams.
3. Implementation: Configure entities, fields, robots, and BPs according to the design.
4. Testing: Execute comprehensive test scenarios covering all branches and error conditions.
5. Deployment: Move to production and monitor initial runs.
6. Handover: Provide documentation and train administrators.

This process minimizes rework and ensures that the automation aligns with your business logic.

Ensuring stability and performance

Low-code tools in Bitrix24 are built on a robust infrastructure, but misconfiguration can lead to performance issues. We apply best practices:

• Use tagged caching settings to optimize robot execution.
• Limit the number of active robots on a single stage to avoid overload.
• Regularly clean up unfinished BPs to maintain database performance.

We also set up monitoring alerts for robot failures and process timeouts, so issues are caught early.

The result is a fully configured low-code ecosystem that reduces routine by 60% and operates without failures. We guarantee stability: if any issues arise within the first month after configuration, we fix them free of charge.

We will evaluate your project within one business day. Contact us to get a consultation and a preliminary work plan. Order low-code configuration today and receive a 10% discount on your first project.

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.