Integration of Bitrix24 with Make (Integromat)

Bitrix24 Integration with Make (Integromat)

Zapier handles simple connections, but when you need branching — "if deal > 100,000 take one route, otherwise another" — or processing an array of products from an order, or retrying on API error, the linear model breaks. Make (formerly Integromat) works differently: visual scenarios with modules, routers, iterators, and error handling. For Bitrix24, this provides flexibility that simpler iPaaS tools lack.

Bitrix24 Module in Make

Make has a full-featured Bitrix24 module with broad API coverage:

Triggers (Watch):

• New/updated leads, deals, contacts, companies
• New tasks and task comments
• Smart process elements (via universal HTTP module)
• Incoming webhooks from Bitrix24

Actions:

• CRUD operations for all CRM entities
• Task management: create, update, delegate, complete
• Timeline management: add comments and activities
• File upload and download from Bitrix24 disk
• Call arbitrary REST API method via Make an API Call

The last point is critical: if standard module action doesn't cover the need — Make an API Call lets you call any Bitrix24 REST API method with custom parameters.

Scenarios with Branching (Router)

Router is the key difference between Make and linear iPaaS. One trigger launches multiple parallel routes with conditions.

Example: processing a new deal in Bitrix24.

[New Deal] → [Router]
              ├── Amount > 100,000 → [Create Project in Planfix] → [Director Notification in Telegram]
              ├── Amount 10,000–100,000 → [Manager Task in Bitrix24] → [Row in Google Sheets]
              └── Amount < 10,000 → [Auto Email to Customer]

Each branch executes independently. Conditions are set via filters on connections between modules.

Working with Arrays (Iterator + Aggregator)

CRM entities in Bitrix24 often contain arrays: product positions in deals, multiple phone numbers, related items. Make processes them via:

• Iterator — splits array into individual elements. Each element passes through subsequent modules separately.
• Aggregator — collects results back into array or single record.

Example: a deal contains 5 product positions. Iterator creates 5 iterations. Each checks inventory in 1C via API. Aggregator collects results and updates the deal: "3 of 5 items in stock".

Error Handling

Make provides built-in error handling tools:

For Bitrix24, Break is especially useful: when API limit is exceeded (2 requests/sec), Make automatically queues the request and retries at set interval.

Error handler binds to specific module. Different strategy can be set for different steps in one scenario.

Scheduling and Triggers

Make supports three scenario run modes:

• Scheduled (Scheduled) — every N minutes. Minimum interval — 1 minute on paid tiers. Watch module checks for new records since last run.
• Instant (Instant) — via webhook. Bitrix24 sends event → Make processes immediately. Setup: Bitrix24 outgoing webhook → Make scenario URL.
• Manual (On Demand) — run by button for testing or one-off tasks.

For production scenarios, we recommend Instant triggers: no delay, no unnecessary API polls, operations consumed only on real events.

Data Mapping and Transformations

Each Make module takes and outputs structured data. Field mapping is through visual interface with access to previous module variables.

Built-in functions:

• String — substring, replace, lower, upper, trim, split
• Numeric — round, floor, ceil, max, min, arithmetic
• Dates — formatDate, parseDate, addDays, dateDifference
• Arrays — map, get, length, slice, merge
• Logical — if, switch, emptystring, ifempty

Example: "Full Name" field from external form needs to split to "First Name" and "Last Name" for Bitrix24 contact.

First Name: {{split(triggerData.fullName; " "; 1)}}
Last Name: {{split(triggerData.fullName; " "; 2)}}

Complex Scenarios for Bitrix24

Catalog sync 1C → Bitrix24

1. Webhook from 1C on product update.
2. Search product in Bitrix24 catalog by SKU (crm.product.list).
3. Router: found → update, not found → create.
4. Update prices in related deals.

Auto-process web form submissions

1. Webhook from site form.
2. Dedup: search contact by email and phone.
3. Create or update contact.
4. Create deal in right pipeline (depends on request type).
5. Distribute to manager via round-robin through Make Data Store.
6. Notify manager in Bitrix24 chat.

Daily pipeline report

1. Run by schedule at 9:00 AM.
2. Get all deals by stages (crm.deal.list with filter).
3. Aggregator: count and sum by each stage.
4. Format text report.
5. Send to leadership Telegram channel.

Make Pricing

Make counts operations — each module in scenario = 1 operation. Scenario with 5 modules consumes 5 operations per run. This is cheaper than Zapier for complex scenarios: in Zapier each step is a separate "task".

For typical Bitrix24 integration (10–20 scenarios, 100–500 events/day), Core tier is sufficient.

What We Configure

• Connect Bitrix24 to Make via OAuth, set up instant webhooks
• Design scenarios: analyze process, choose modules, map data
• Implement branching, iterators, and aggregators for complex logic
• Set up error handling: strategy for each critical module
• Optimize operation spending: combine modules, filters, conditional branches
• Test scenarios on real data and monitor in production
• Document: each scenario schema, logic description, contacts