Bitrix24 Integration with Project Management Systems
A company works in Bitrix24, but the project team tracks tasks in Asana. The client requires a report in MS Project. The manager spends half a day transferring data manually — copying statuses, updating deadlines, recalculating progress. Errors are inevitable, data becomes outdated before sending. Integration between systems eliminates manual transfer and provides unified project view.
Typical Integration Scenarios
| Integration | Direction | Transferred |
|---|---|---|
| B24 → MS Project | Export | Tasks, deadlines, dependencies, progress → .mpp or .xml file |
| B24 ↔ Asana | Bidirectional | Tasks, statuses, responsible, comments |
| B24 ↔ Monday.com | Bidirectional | Tasks, stages, custom fields |
| B24 ← Jira | Import | Tickets from Jira → tasks in B24, status sync |
Bidirectional synchronization means: create task in Asana — it appears in B24. Change status in B24 — it updates in Asana. No duplication, no manual control.
Bitrix24 REST API for Tasks
Foundation of any integration — REST API. Key methods:
-
tasks.task.add— create task -
tasks.task.update— update fields (status, deadlines, responsible) -
tasks.task.list— get task list with filters -
tasks.task.get— details of specific task -
task.commentitem.add— add comment
To track changes — onTaskUpdate event (webhook). On task update, B24 sends POST request to specified URL with change details.
Integration Through iPaaS Platforms
Direct API integration requires development. Alternative — iPaaS platforms (Integration Platform as a Service): Albato, Make (Integromat), n8n, Zapier. Principle:
- Trigger — event in one system (task creation in Asana).
- Mapping — field matching (Asana "Assignee" → B24 "Responsible").
- Action — operation in second system (create task in B24 via REST API).
Field mapping is key. Statuses don't match across systems: in Asana — "In Progress," in B24 — Kanban stage "In Development." Mapping table is created before configuration starts.
MS Project Export
MS Project works with .mpp and .xml formats. B24 doesn't export to .mpp directly. Options:
-
XML Export. Script exports tasks from B24 via
tasks.task.list, forms XML in MS Project format. Dependencies, deadlines, resources — everything maps to Project XML structure. - CSV Intermediate. Export tasks to CSV, import to MS Project with manual column mapping.
- Power Automate. For Microsoft 365 organizations — B24 connector → Power Automate → MS Project Online.
What We Configure
- Designing integration scheme: sync direction, data set to transfer, conflict rules
- Field and status mapping between B24 and external system
- Setting up integration through iPaaS (Albato, Make, n8n) or direct development via REST API
- Creating webhooks for real-time change tracking
- Exporting/importing data to MS Project (XML, CSV)
- Testing: verifying sync on task create, update, delete in both directions