Skip to content
N1

About me: 5 years in Bitrix24, large-scale integrations and Laravel development

I've worked with Bitrix24 for 5 years: from small fixes to operations automation for entire business centers and dealer networks. Below — real projects by date, who I fit, official paperwork and the stack I currently work with.

5+
years of experience
50+
integrations
100+
automated processes
10+
business industries
Own code
not a Bitrix24 drag-and-drop builder

Tasks I have already worked on

CRM and sales
  • Bitrix24 ↔ MoySklad
  • Bitrix24 ↔ 1C
  • Mobile visit forms
  • Automatic reports
  • Approval systems
Checks and scoring
  • TrustMe
  • PKB
  • ADATA
HR and communications
  • Huntflow
  • HeadHunter
  • HR bots
  • Telegram bots
Auth and cabinets
  • OTP auth
  • QR registration
  • Client cabinets

Latest projects

August 2026
Floor plans and occupancy analytics for a business center network
An embeddable interactive floor-plan builder with CRM occupancy auto-synced via cron — for a network of business centers including Big Tech.
Stack: Bitrix24 (catalog, cron), PHP, embeddable JS widget
Result: Across the network: 93 floors, 1,087 offices and 152 floor plans — occupancy updates from the CRM automatically.
Learn more →
July 2026
Operations automation for the Big Tech business center
Telegram bots for clearing parking debt and registering tenants, security QR patrols and staff onboarding on top of Bitrix24.
Stack: Bitrix24 D7, Telegram Bot API, PHP, cron agents
Result: Clearing a parking debt and registering a tenant are now handled by a bot instead of a call to the front desk.
Learn more →
June 2026
Face ID attendance tracking via Hikvision
An hourly Bitrix24 agent polls Hikvision Face ID terminals over ISAPI and assembles an attendance timesheet.
Stack: PHP, Hikvision ISAPI (digest auth), Bitrix24 agent (cron)
Result: Face ID turnstile data is collected into one timesheet every hour instead of staying on the terminals.
Learn more →
May 2026
Laravel Client Cabinet
A client cabinet: authentication, roles, requests, messages, invoices, CRM integration.
Stack: Laravel, Vue/Inertia, PostgreSQL, Redis
Result: Part of the inquiries moved to self-service.
Learn more →
February 2026
Bitrix Client Cabinet
A client cabinet on Bitrix24: request statuses, inquiries, invoices, connection to CRM data.
Stack: Bitrix D7, HL blocks, REST/OpenLines
Result: Clients see statuses without calling support.
Learn more →
January 2026
Bitrix24 ↔ MoySklad
Sync of companies, contacts and deals: mapping, duplicate search, logging.
Stack: Bitrix24, MoySklad API, PHP, queues
Result: An exchange history appeared — it is clear where sync fails.
Learn more →
December 2025
A custom BI dashboard on top of Bitrix24
20 parameterized SQL reports on top of live CRM data: a lead-to-visit-to-sale funnel with a multi-level cache.
Stack: PHP, Bitrix24 D7, SQL reports, TTL cache, whitelisted AJAX
Result: Management and the call center got a single funnel dashboard instead of Excel exports.
Learn more →
October 2025
Event-driven Bitrix24 integration via Kafka
Exchange with the CRM over Kafka instead of one-off HTTP calls: deals matched by business key, with Telegram alerts on failures.
Stack: Node.js, Kafka (kafkajs), Bitrix24 REST, Azure AD, Telegram alerts
Result: The exchange became event-driven: a failure no longer loses the event or stays silent — there's retry and an alert.
Learn more →
August 2025
Bitrix24 ↔ 1C synchronization
SOAP/HTTP exchange with several 1C databases plus a web approval subsystem with an "approve straight from the email" trigger.
Stack: Bitrix24 D7, 1C (SOAP/HTTP), PHP, cron, email triggers
Result: Requests and stock levels stopped drifting apart manually — proven on two independent rollouts.
Learn more →
June 2025
Car selection and deal processing right in the CRM
Vehicle and add-on selection right inside the deal card, with a live link to stock and the work order from 1C.
Stack: Bitrix24 Smart Process, D7, custom fields, modals, 1C (stock/work order)
Result: A manager closes the deal without leaving the card: from choosing the car to payment and the contract.
Learn more →
April 2025
HR processes in Bitrix24: onboarding and absence tracking
A full onboarding process on Bitrix24 business processes and a Telegram bot for time off that auto-triggers approvals.
Stack: Bitrix24 Business Process, Telegram Bot API, PowerBI (custom dashboard), PHP
Result: Onboarding and absence tracking became a process with a history, not chat threads.
Learn more →
January 2025
A client cabinet built on top of Bitrix24
Separate client authentication with no Bitrix user accounts, role-based CRM field visibility and secure document delivery.
Stack: Bitrix24 D7, HL blocks, PHP, CSRF/rate-limiting, secure file delivery
Result: Clients got self-service without direct CRM access — in a separate, protected cabinet.
Learn more →

Integrations I have worked with

Real experience across systems and services

An integration is not just sending a REST request. You need mapping, duplicate protection, handling of partial errors, retry and logging.

1 Do not lose data 2 Do not create duplicates 3 Do not fail silently 4 Provide clear logs
CRM / ERP
Bitrix24 1C MoySklad
HR
HeadHunter Huntflow
Checks / scoring
TrustMe ADATA PKB
Communications
Telegram WhatsApp Instagram Asterisk
Infrastructure
Docker GitHub Actions Nginx VPS
Databases / data
MySQL PostgreSQL Redis SQL / BI

Who I work with

  • Small and medium business on Bitrix24
  • Sales departments and call centers
  • Car dealerships and service companies
  • Financial / scoring processes
  • HR teams
  • Companies with legacy CRM
  • Businesses where data moves between CRM, ERP, warehouse and external services

I work officially

Contract Invoice Closing documents Prepayment Final payment after acceptance Retainer support by agreement

Why they choose me

Not just "set up an integration" — I leave logs and clear diagnostics.
Not just "fixed a bug" — I explain the cause and what might break next.
Not just "wrote code" — I leave a structure you can maintain.
Not just "did it via REST" — I pick REST, D7 or a separate backend by load.
I do not hide risks — I say where an audit is needed and where a fixed price cannot be promised.
I do not disappear after release — I support and fix by logs.
Integration Hub

This is an integration hub itself

This site is not just a business card. Inside there is a private admin for tasks, clients, requests and future integrations.

Requests from the site Tasks Projects Clients Integrations Integration logs

Currently working with

Go Laravel 13 AI Agents Asterisk ARI Event-driven architecture

Not sure where to start?

Just describe the problem. I will study the current solution, assess the risks and propose implementation options.