← Back to blog
AutomationJune 26, 2024· 7 min read
1C ↔ Bitrix24: an integration that doesn't break monthly
Over three years we've fixed other people's 1C ↔ Bitrix integrations 20+ times. Sharing the architecture that survives either side's updates.
Creastra Digest
- A bus in the middle, not a direct p2p call
- Idempotent messages — a retry won't double an order
- JSON-schema contract, versioned in git
Direct 1C → Bitrix → 1C integration is a tech-debt ticket. After either side's update you wake up Monday with no orders.
The bus architecture
1C writes events to RabbitMQ; an adapter reads, normalises, passes to Bitrix. Reverse path is identical. If Bitrix is down for 4 hours, the queue holds. If 1C updates, you only patch the adapter.
Idempotency
Every message carries a UUID. The receiver has a "processed" table. A repeated UUID is a no-op. This saved us from duplicate orders at least 6 times last year.