Bitrix24 Integration with Make (Integromat) Setup
Standard integrations via Zapier handle simple links, but when branching by deal amount, processing an order array, or retrying on API error is needed, 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 solutions lack. We configure such integrations turnkey: we evaluate your project in 1 day, assemble the scenarios, and hand over documentation. Our experience includes over 50 complex integrations, and we guarantee stable 24/7 scenario operation.
Why Make is Better for Bitrix24 than Zapier
Make has a full-fledged module for Bitrix24 with extensive API coverage. Unlike Zapier, you can build scenarios with branching (Router), process arrays via Iterator/Aggregator, and handle errors flexibly. Additionally, Make is cheaper for complex scenarios: each step is one operation, not a separate "task". For example, a scenario with 10 modules on the Core plan costs a fraction of a cent per run, while Zapier would charge 10 tasks.
Bitrix24 Module in Make
Triggers (Watch):
- New/updated leads, deals, contacts, companies
- New tasks and task comments
- Smart process items (via universal HTTP module)
- Incoming webhooks from Bitrix24
Actions:
- CRUD operations for all CRM entities
- Task management: create, update, assign, complete
- Timeline management: add comments and activities
- Upload and download files from Bitrix24 Drive
- Call any REST API method via Make an API Call
The last point is critical: if the standard module action doesn't cover the need, Make an API Call allows calling any REST API method with arbitrary parameters.
Scenarios with Branching (Router)
Router is a key difference of Make from linear iPaaS. One trigger launches several parallel routes with conditions.
Example: processing a new deal in Bitrix24.
[New Deal] → [Router]
├── Amount > 100,000 → [Create project in Planfix] → [Notify director via Telegram]
├── Amount 10,000–100,000 → [Task to manager in Bitrix24] → [Row in Google Sheets]
└── Amount < 10,000 → [Automatic email to client]
Each branch executes independently. Conditions are set via filters on connections between modules.
Working with Arrays (Iterator + Aggregator)
Bitrix24 CRM entities often contain arrays: deal product items, multiple contact phones, related items. Make processes them via:
- Iterator — splits an array into individual items. Each item passes through subsequent modules separately.
- Aggregator — collects results back into an array or a single record.
Example: a deal contains 5 product items. Iterator creates 5 iterations. Each checks product availability via 1C API. Aggregator collects results and updates the deal: "3 out of 5 items in stock."
How to Set Up Error Handling in Make?
Make provides built-in tools for error handling:
| Directive | What it does | When to use |
|---|---|---|
| Ignore | Skip the error, continue scenario | Non-critical actions (notifications) |
| Resume | Substitute default value and continue | Missing data |
| Rollback | Rollback all actions of the scenario | Transactional operations |
| Commit | Commit the performed actions, stop scenario | Partial execution acceptable |
| Break | Queue execution and retry later | Temporary API errors (rate limit) |
For Bitrix24, Break is especially useful: when exceeding the API limit (2 requests/sec), Make automatically queues the request and retries after a set interval.
Scheduling and Triggers
Make supports three scenario launch modes:
- Scheduled — every N minutes. Minimum interval is 1 minute on paid plans. The Watch module checks if new records have appeared since the last run.
- Instant — via webhook. Bitrix24 sends an event → Make processes immediately. Setup: outgoing webhook from Bitrix24 → scenario URL in Make.
- On Demand — manual launch 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 accepts and returns structured data. Field mapping is done through a visual interface with access to variables from previous modules.
Built-in functions:
- String:
substring,replace,lower,upper,trim,split - Numeric:
round,floor,ceil,max,min, arithmetic - Date:
formatDate,parseDate,addDays,dateDifference - Array:
map,get,length,slice,merge - Logical:
if,switch,emptystring,ifempty
Example: the "Full Name" field from an external form needs to be split into "First Name" and "Last Name" for a Bitrix24 contact.
First Name: {{split(triggerData.fullName; " "; 1)}}
Last Name: {{split(triggerData.fullName; " "; 2)}}
Complex Scenarios for Bitrix24
1C to Bitrix24 Product Catalog Synchronization
- Webhook from 1C on product update.
- Search for product in Bitrix24 catalog by SKU (
crm.product.list). - Router: found → update, not found → create.
- Update prices in related deals.
Automatic Processing of Website Leads
- Webhook from site form.
- Deduplication: search for contact by email and phone.
- Create or update contact.
- Create deal in the appropriate pipeline (depends on lead type).
- Distribute to manager via round-robin using Make Data Store.
- Notify manager in Bitrix24 chat.
Daily Funnel Report
- Scheduled run at 9:00.
- Get all deals by stages (
crm.deal.listwith filter). - Aggregator: count and sum per stage.
- Generate text report.
- Send to management Telegram channel.
Make Pricing
Make counts operations — each module in a scenario = 1 operation. A 5-module scenario consumes 5 operations per run. This is cheaper than Zapier for complex scenarios: in Zapier, each step is a separate "task."
| Make Plan | Operations/month | Scenarios | Minimum Interval |
|---|---|---|---|
| Free | 1,000 | 2 | 15 min |
| Core | 10,000 | Unlimited | 1 min |
| Pro | 150,000 | Unlimited | 1 min + instant |
For a typical Bitrix24 integration (10–20 scenarios, 100–500 events per day), the Core plan is sufficient. The cost per run of a 5-module scenario is 5 operations, which at the Core plan is a fraction of a cent.
What's Included in Integration Setup
- Connecting Bitrix24 to Make via OAuth, setting up instant webhooks
- Designing scenarios: process analysis, module selection, data mapping
- Implementing branching, iterators, and aggregators for complex logic
- Configuring error handling: strategy for each critical module
- Optimizing operation consumption: merging modules, filters, conditional branches
- Testing scenarios on real data and monitoring in production
- Documentation: diagram of each scenario, logic description, contact persons
Contact us to get a timeline and cost estimate for your project. We provide free consultation on integration architecture. Get a consultation for your project — we will assess the timeline and choose the optimal integration architecture.