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.