Documentation lives in Notion, deals and tasks in Bitrix24. A manager closes a deal, then manually goes to Notion to update the project table. A developer records requirements in Notion, then duplicates them into a Bitrix24 task. A month later, both systems show different pictures—versions diverge. Manual copying guarantees desynchronization, and each mistake costs team time. We automate data exchange: two-way synchronization via middleware that eliminates losses and duplicates. Savings on manual operations reach 75% of labor costs, and the integration pays for itself within 2–3 months.
How to set up two-way synchronization between Bitrix24 and Notion?
The connection works through Notion API and Bitrix24 REST API. Notion provides v1 API for working with databases, pages, and blocks. Bitrix24 offers webhooks for subscribing to CRM, tasks, and business process events. Between them is a middleware server on PHP 8.1+ that listens to events from both sides and transmits data. The middleware-based connection is 3 times more reliable than direct REST requests due to error handling and rate limits.
Bitrix24 (CRM/task event) → Webhook → Middleware → Notion API → Database/Page
Notion (polling/webhook) → Middleware → Bitrix24 REST API → CRM/tasks
Notion API does not yet support native webhooks for tracking changes. Middleware uses polling—querying the Notion database with a last_edited_time filter every 30–60 seconds. For Bitrix24, standard webhooks via event.bind work.
Synchronization of Notion databases with CRM
The main scenario is mirroring CRM records to a Notion database. We configure field mapping:
| CRM Bitrix24 Field |
Notion Database Property |
Type |
| TITLE (deal name) |
Name (title) |
title |
| STAGE_ID |
Status |
select |
| OPPORTUNITY |
Amount |
number |
| ASSIGNED_BY_ID |
Responsible |
people / rich_text |
| COMPANY_ID → TITLE |
Company |
rich_text |
| DATE_CREATE |
Date created |
date |
| UF_* (custom fields) |
Custom properties |
per type |
When a deal stage changes in Bitrix24 (ONCRMDEALUPDATE event), middleware updates the corresponding entry in Notion via PATCH /v1/pages/{page_id} with the new select property value. In the reverse direction—when the status changes in Notion, middleware calls crm.deal.update.
What difficulties arise when integrating Bitrix24 with Notion?
Rate limits. Notion API limits 3 requests per second per integration. Middleware queues requests and maintains the interval. On 429 Too Many Requests—exponential backoff. Payload size: a maximum of 100 blocks per POST /v1/pages. For large documents, middleware splits content into multiple PATCH /v1/blocks/{block_id}/children.
Data drift. Middleware stores a mapping table b24_entity_id ↔ notion_page_id. On update, it checks the source to avoid loops: Bitrix24 updates deal → middleware sets sync_source = "b24" and updates the Notion page. On next polling, middleware sees the change but compares timestamps—if the update occurred within 10 seconds after the middleware write, it is skipped. For text fields—last write wins strategy; for statuses—configurable priority (master system can be specified).
Comparison of approach with and without middleware
| Criterion |
Direct REST requests |
Middleware |
| Reliability |
Low—packet loss |
High—queue and retry |
| Errors |
Rate limit blocks |
Exponential backoff |
| Mapping |
Manual in each script |
Centralized config |
| Audit |
No |
Logging of every request |
| Maintenance complexity |
High |
Low—single component |
Creating pages from CRM events
When an event occurs in Bitrix24, middleware automatically creates a page in Notion with pre-filled content:
- New deal → page in the "Projects" database with client details, amount, responsible. Page body contains a template: sections "Requirements", "Timeline", "Contacts".
- Won deal → page in the "Active Projects" database with automatic transfer of data from the deal card.
- New task → entry in the Notion kanban base linked to the project.
Creating a page is a POST /v1/pages call with parent.database_id and an array of properties. Content is passed as a block array: paragraph, heading_2, to_do, table.
Technical details of batch processing implementation
When synchronizing large volumes (more than 100 records), middleware uses a queue: the list of changes is accumulated and sent in batches with an interval. Each batch is confirmed, on error—repeat after 5 seconds. For Notion, sequential calls with a pause are used since the bulk method is not yet available.
How is data consistency ensured during simultaneous editing?
Middleware uses timestamps: if both sides change the same object almost simultaneously, the last write wins rule applies, with the ability to set a priority system. All conflicts are logged, and the administrator receives a notification. Additionally, manual confirmation mode can be enabled for critical fields.
What is included in the integration setup
- Audit of current processes and data structure (Notion Database, CRM, tasks).
- Prototype middleware on PHP 8.1+ with a proven stack (Laravel or Symfony, PDO, Redis for queues).
- Development of field mapping between CRM and Notion properties.
- Configuration of Bitrix24 webhooks and Notion polling with custom intervals.
- Operational documentation and disaster recovery procedures.
- Team training (1-hour session).
- 2 weeks of post-launch support.
Why trust our team with the integration?
We are engineers with 5+ years of experience in the 1C-Bitrix ecosystem and Notion. We have 50+ successful integrations for companies from the CIS and Europe. We understand how internal mechanisms work: infoblocks, HL-blocks, tagged caching, CommerceML, exchange with 1C. We use only stable middleware versions and test under excessive loads. Order a consultation—we will analyze your data scheme and propose the optimal integration architecture. Contact us to discuss the details of your project.
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
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
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
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- 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.
