Bitrix24 with 1C-Bitrix Integration: Site & Portal
A site on 1C-Bitrix lives separately from the Bitrix24 portal. Requests from web forms go to email and get lost. Online orders are not visible in CRM. A manager finds out about a new client only when the client calls back asking "where's my order?" Both products are from Bitrix, and a logical connection exists but is not configured by default. It needs to be configured and refined — that's what we do. When a site receives 50 requests per day and managers spend 10–15 minutes copying data from email to CRM, it's a direct loss. Our team has 10+ years of experience in integrating the 1C-Bitrix and Bitrix24 ecosystem, we guarantee results and long-term support.
What problems does integration solve?
-
Lost leads — each filled form turns into a CRM lead with UTM tags, eliminating manual entry. Processing time reduces from 10 seconds to automatic creation.
- No unified sales picture — orders from the online store automatically create deals with product items.
- Disjointed communications — the online chat on the site works in conjunction with open lines and CRM.
- Manual status synchronization — a status change in CRM updates in the client's personal account. Typical delay without integration is up to 1 hour.
How to automatically transfer leads from web forms to CRM?
Any form on the site (request, callback, subscription) should create a lead in CRM automatically. This is implemented via the Bitrix24 REST API. On form submission, the OnAfterResultAdd event handler triggers and forms a request:
POST https://portal.bitrix24.ru/rest/{user_id}/{webhook_token}/crm.lead.add
The fields transmitted: TITLE, NAME, PHONE, EMAIL, SOURCE_ID, UTM tags, and COMMENTS. UTM tags are stored in a cookie on first visit — this is critical for analytics. Before creating a lead, we check for duplicates via crm.duplicate.findbycomm. If a contact already exists, a deal is created, not a new lead. The budget saved on routine operations after integration depends on the scope of work.
Why is reverse status synchronization important?
Managers often change order status in CRM, but the client sees outdated information on the site. We configure webhooks from Bitrix24: when the deal stage changes, the site receives a notification and updates the record in b_sale_order. This works for any number of statuses. Comparison: webhooks are faster and simpler than periodic agents — update time drops from hours to seconds. In CRM, you can set up business processes (Bizproc) for automatic lead processing according to set rules.
Synchronization of orders and catalog
For an online store, we set up two-way exchange:
| Event on site |
Action in B24 |
| New order |
crm.deal.add + crm.deal.productrows.set |
| Status change |
crm.deal.update — new stage |
| Payment |
Stage "Paid" + record in timeline |
| Cancellation |
Deal "Lost" with reason |
Products from information blocks are exported to the B24 catalog daily via cron. Field mapping: name, SKU, price, description, image. For catalog synchronization, the CommerceML format is used — the standard exchange protocol between 1C and Bitrix. 1C-Bitrix documentation recommends using REST API for reliable synchronization.
| Integration method |
Implementation speed |
Flexibility |
| Standard module |
1–2 days |
Low — only basic scenarios |
| REST API |
3–5 days |
High — any custom fields and events |
| Webhooks |
1 day |
Medium — one-way flow |
What is included in the work
- Setting up REST API bridge between site and portal
- Implementing handlers for all types of forms and orders
- Integrating online chat widget with CRM binding
- Developing rules for status and field mapping
- Architecture and access documentation
- Training your managers to work with the new link
- Post-release support for one month
Work process
- Analytics — study site structure, form types, order schemas.
- Design — define integration points, prepare API specification.
- Implementation — write code, configure handlers.
- Testing — check all scenarios (creation, modification, duplicates, errors).
- Deployment — roll out to production environment, set up monitoring.
Timeline and cost
Timeline: from 2 days to 3 weeks depending on complexity (typical project — 1–2 weeks). Cost is calculated individually after analysis. Discount available for complex integration. Contact us for a project evaluation — we'll consult and propose the optimal solution. Order turnkey integration: you get a working link with documentation.
Typical mistakes in self-integration: missing duplicate handling (multiple leads for one client), loss of UTM tags due to incorrect cookie storage, missing API errors (data submission failure goes unnoticed), field type mismatches (e.g., passing a string instead of numeric ID). Our integration eliminates these problems.
Integration saves up to 20 hours of managers' work per month — automation pays off quickly. We guarantee stability and full transparency.
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.
