Kwork orders land in the Bitrix24 funnel automatically
Custom Kwork ↔ Bitrix24 CRM integration
Bitrix24 deals kanban: Kwork orders in one funnel with stages and amounts
Problem
Kwork orders were copied by hand: managers typed client, service and amount into Bitrix24, lost statuses and risked duplicate deals.
Solution
A custom integration contour: each Kwork order automatically creates or updates a Bitrix24 deal — with client, service, amount and status.
Result
A live CRM funnel: orders (including ML/Python) show on the board with stages and amounts; the team works in Bitrix24 instead of copying from the marketplace.
How it works
- An order appears for the seller on Kwork
- The contour fetches the order (session pull, capture, or webhook)
- Client, service and amount map into Bitrix24 fields
- Create or update the deal — no duplicates
- Amount and Kwork status are written into the CRM card
- Sync log and per-order error handling without losing the batch
Production-grade contour
- Deduplication by ORIGIN_ID — re-runs do not create duplicate deals
- Update of an existing deal instead of a second create
- Sync journal (state file + logs): created / updated / errors
- Kwork status is written into the card (source and comments)
- Webhook secret protection and Bitrix24 OAuth token refresh
Why not a ready-made connector
Why not a ready-made connector: Kwork has no public API for our scenario, and third-party SaaS like ApiMonster does not give the control we need over fields and deduplication. A custom contour — without depending on someone else’s middleware.