Problem: during two-way synchronization between 1С:Document Management (1С:DO) and Bitrix24, webhooks loop — updating a document in 1С creates a task in Bitrix24, updating the task sends a request back to 1С, and the cycle repeats. Without sync flags, this leads to data duplication and endless notifications. We solve this via control markers and intelligent mapping, ensuring stable operation of the bundle.
The 1С:Document Management and Bitrix24 bundle bridges the gap between the accounting circuit and the team workspace. Documents are stored in 1С:DO with legal force and versioning, while employees work with tasks and approvals inside Bitrix24 — without switching between systems. Our experience in this integration exceeds 5 years, with over 100 implementations, allowing us to avoid typical setup mistakes.
We configure two-way exchange so that changes in either system are correctly reflected in the other, conflicts are handled automatically, and approval routes are not duplicated. Everything works turnkey: from initial setup to monitoring in production.
What Gets Synchronized
Exchange is built in three directions:
- Documents → Bitrix24 Drive. Files from 1С:DO are published to specified folders on Drive. When a version is updated in 1С:DO, the file on Drive is overwritten. Reverse upload — by trigger or schedule.
- Assignments ↔ Tasks. An assignment in 1С:DO creates a task in Bitrix24 linked to the responsible person. Closing the task in B24 changes the assignment status in 1С:DO.
- Approvals via business processes. The approval route for a document in 1С:DO is translated into a Bitrix24 business process — participants receive notifications and vote inside the portal.
Technical Integration Stack
The exchange is implemented via Bitrix24 REST API. Official documentation and 1С:DO HTTP services. Interaction scheme:
| Component | Role |
|---|---|
| Bitrix24 REST API | Creating tasks, uploading files to Drive, launching business processes |
| Incoming webhooks | Receiving events from 1С:DO — new document, status change |
| Outgoing webhooks | Notifying 1С:DO about approval completion in B24 |
| 1С:DO HTTP service | Endpoint for receiving commands from Bitrix24 |
| Message queue | Buffering under peak loads (optional — RabbitMQ) |
Authorization — via OAuth 2.0 for server applications or incoming webhook with token. For production, we use a server application: token renews automatically, no tie to a specific user.
Field Mapping
Directories in 1С:DO and Bitrix24 do not match. We configure a correspondence table:
- 1С:DO Counterparties → CRM Companies. Matching by TIN or external code.
- Document types → Drive folders. Each document type from 1С:DO is linked to a specific folder.
- Executors → B24 Users. Mapping by email or employee number in a custom field.
- Approval statuses. "Approved" / "Rejected" / "Revision" in 1С:DO correspond to voting results in Bitrix24 business processes.
How to Set Up Approval Routes?
This is a key element of integration. The route in 1С:DO contains stages: initiation, sequential or parallel approval, signing. In Bitrix24, this route is reproduced through a business process template:
- Initiation. A webhook from 1С:DO launches a business process in Bitrix24 with the document ID, list of approvers, and deadline.
- Parallel stage. The business process creates assignments for all stage participants simultaneously. The result is recorded in BP variables.
- Sequential stage. The next participant's assignment is created only after the previous one completes.
- Result return. Upon BP completion, an outgoing webhook sends the final status and approvers' comments to 1С:DO.
If the route in 1С:DO changes (stage added, approver replaced), the BP template is updated manually or via a re-creation script. Full auto-generation of BP templates from 1С:DO is possible but requires separate development effort.
How Are Conflicts Handled?
In two-way exchange, collisions are inevitable. Resolution rules:
- Documents. Priority to 1С:DO as the accounting system. If a file is changed in both systems, the version from 1С:DO overwrites the Drive version; the conflicting copy is saved with the suffix
_conflict_YYYYMMDD. - Tasks/assignments. Priority to the system where the last change occurred (by timestamp). If discrepancy is less than 60 seconds — manual resolution via notification to admin.
- Approvals. Conflict is structurally impossible: the voting result is formed in one system and passed to the other.
How to Set Up Schedule and Monitoring?
Document synchronization runs on a schedule (cron task on 1С side, agent on B24 side) with an interval from 5 minutes. Tasks and approvals — in real-time via webhooks.
For monitoring, we configure:
- Exchange log in 1С:DO (information register with history of sends)
- Incoming webhooks log in Bitrix24
- Admin notification on HTTP errors (4xx/5xx statuses) or timeout
Typical Problems and Solutions
| Problem | Solution |
|---|---|
| Webhook looping | Add synchronization flag and check timestamps |
| Task duplication | Set a unique identifier for each assignment |
| Document version loss | Use message queue for guaranteed delivery |
For an individual integration plan, get a consultation — we will analyze your document workflow scheme.
What You Get in the End
Employees approve documents in the familiar Bitrix24 interface without entering 1С:DO. Accountants and lawyers continue to work in 1С:Document Management. Both systems contain up-to-date data with a delay of no more than 5-10 minutes for documents and instant synchronization for tasks and approvals. Our approach with message queues (RabbitMQ) handles up to 5,000 documents per hour — 10 times faster than typical solutions without buffering.
Evaluate your project: we will prepare an integration plan in 1 day. Contact us for a consultation — we guarantee stable operation of the exchange.