Bitrix24 ↔ 1C synchronization
Expense and travel requests, stock levels and employee data were synced between 1C and the CRM by hand — approvals got lost and data drifted apart.
Several independent 1C databases with different data schemas, the need to accept incoming data from 1C safely, the requirement not to lose approval status on failures.
- SOAP/HTTP exchange with several 1C databases: warehouses, employees, business trips
- A web approval subsystem with an "approve straight from the email" trigger
- Receiving stock/inventory updates via a source-checked webhook
- Syncing approval status back into the CRM
- Exchange logging for troubleshooting failures
Requests and stock levels stopped drifting apart manually, approvals got faster — the approach was proven on two independent rollouts with different 1C setups.
Related services and solutions
Bitrix24 D7: boxed development and stabilization
I work not only with interface settings, but at the level of the box, the code and internal APIs.
Business process automation
When employees transfer data manually, reconcile spreadsheets, lose requests or repeat the same actions — I turn the routine into code.