Integrate Bitrix24 and Trello: Task Synchronization via Middleware

Typical scenario: your content plan lives in Trello, your deals and tasks live in Bitrix24. Without integration, you manually copy each card—losing deadlines, files, and comments. A designer finishes a task in Trello, but Bitrix24 still shows "In Progress." Reconciliation eats hours, sometimes days. We've seen projects where manual sync consumed up to 5 hours per week—after middleware implementation, that time dropped to zero.

Our middleware listens to webhooks from both systems and syncs data in real time. Automation is 10 times faster than manual syncing. With 10+ years of experience with Bitrix24 REST and Trello API, we have delivered over 50 integrations. Integration cost starts at $2,500 and pays for itself within a few months. Clients save up to $500 per month compared to manual data transfer.

How Synchronization Works

Trello provides a REST API and webhooks; Bitrix24 offers REST API with outgoing webhooks on events. The middleware sits between them, handling three tasks: receive events, transform data, and send updates to the paired system.

Trello (webhook) → Middleware → B24 REST API → task/CRM
B24 (event) → Outbound Webhook → Middleware → Trello REST API → card

Each Trello board – Bitrix24 project pair is configured individually. One board can sync with one project, multiple boards with multiple projects.

Mapping Structures

Trello and Bitrix24 organize work differently. The mapping:

Description conversion: Trello stores Markdown, Bitrix24 uses HTML. The middleware parses and converts in both directions. Images in descriptions are downloaded and re-uploaded.

{
  "sourceBoard": "5a2c3d4e5f",
  "targetProject": "group_42",
  "listMapping": {
    "backlog_list_id": "NEW",
    "progress_list_id": "IN_PROGRESS",
    "done_list_id": "COMPLETED"
  },
  "userMapping": {
    "trello_user_email": "bitrix_user_email"
  }
}

Status Synchronization via Lists

Moving a card between lists in Trello changes its status. The updateCard webhook with listAfter field tells the middleware which list the card moved to. The middleware looks up the mapping table and updates the task stage in Bitrix24.

Reverse direction: when a task stage changes in Bitrix24 (event ONTASKUPDATE), the middleware moves the Trello card to the corresponding list via PUT /1/cards/{id} with idList parameter.

The list mapping table is configured per board:

Automation via Power-Ups and REST API

Trello Power-Ups allow adding buttons and actions on cards. The middleware provides an endpoint for a Power-Up that adds a "Create in B24" button. When clicked, the card becomes a task in the selected Bitrix24 project.

On the Bitrix24 side, a robot in task business processes triggers when a task with a specific tag (e.g., "trello") is created. The robot calls a webhook on the middleware, which creates a Trello card on the appropriate board.

Additional automations:

• Card moved to "Done" → task closed in Bitrix24 + comment with timestamp
• New comment on card → comment on Bitrix24 task (and reverse)
• Member added to card → observer added to Bitrix24 task
• Deadline changed in Bitrix24 → due date updated on Trello card

Migration from Trello to Bitrix24

A common scenario: the team moves entirely from Trello to Bitrix24. The middleware supports full migration:

1. Export boards. Via Trello API (GET /1/boards/{id}/cards), all cards with checklists, comments, attachments, and labels are retrieved.
2. Create structure. Bitrix24 projects (groups) matching the boards are created; kanban stages are set up according to Trello lists.
3. Transfer cards. Each card is created as a task via tasks.task.add. Checklists via task.checklistitem.add. Comments via task.commentitem.add with correct author and date.
4. Files. Attachments are downloaded from Trello, uploaded to Bitrix24 disk, and attached to tasks.
5. Archived cards. Transferred as completed tasks with history preserved.

Migration volume: a 500-card board takes 15–30 minutes (depends on attachment count and API limits).

Real-Time Two-Way Sync: No Delays

The key is an asynchronous queue with rate limiting. Trello API limits: 100 requests per 10 seconds per token, 300 per 10 seconds per key. Bitrix24: 2 requests per second. The middleware manages throttling and batch requests in Bitrix24 using the batch method (up to 50 commands per call). For Trello, fields and card_fields parameters reduce request count (only fetch needed fields). This architecture enables real-time sync—delay typically under 10 seconds. Manual copying takes hours; automation takes minutes—a 10x speedup.

Why User Mapping Matters

Without mapping, card participants are not attached to tasks—the task ends up with no assignee. The middleware matches email or Trello user IDs with Bitrix24 employees. If no match, it can create a user or use a default assignee. This prevents context loss.

What's Included in Our Service

• Development and deployment of middleware (your server or cloud)
• Configuration of structure mapping: boards → projects, lists → stages, fields → fields
• Setup of two-way synchronization for statuses, comments, deadlines, and attachments
• Integration of Power-Ups and business processes
• Full data migration if needed
• Operations documentation
• Technical support for 30 days after launch

We guarantee a personalized timeline and cost estimate after a free consultation — get in touch to see how automation pays off.

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Additional integrations that deliver real value:

• Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
• IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
• Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
• EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

• role model via CGroup and section‑level permissions;
• two‑factor authentication (OTP, Yandex.Key, SMS);
• audit of all actions (b_event_log);
• TLS encryption for transmission and disk encryption;
• full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

• Project documentation: architecture, integration scheme, business process diagrams.
• Configured portal with all integrations (1C, AD, telephony, EDI).
• Business process descriptions and instructions for administrators and users.
• 30 days of technical support after launch.
• Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.