Resources · Make integration

Bitrix24 Make integrationAutomate Bitrix24 with Make.

Can Make keep your Bitrix24 CRM in step with the rest of your tools, without code? The Bitrix24 Make integration gives you 37 modules, 6 of them triggers, across contacts, companies, leads, deals, invoices and tasks. Below, you connect your account and build a first scenario step by step.

Try the Bitrix24 integration on MakeSee the 37 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Bitrix24 Make integration let you automate?

The Bitrix24 Make integration links your Bitrix24 account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule. A module is one brick of that chain, such as a trigger that spots a deal event or an action that creates a task, so records move between Bitrix24 and your other apps without copy and paste.

Leads that get a follow-up. Watch Leads picks up the lead event you choose at each scheduled check, and Create a Task hands the prospect to a salesperson. Add a Checklist to a Task then writes out the calls to make, so the first contact never depends on memory.

One clean customer record. When a sign-up arrives from a form tool or a spreadsheet, Search Contacts checks whether the person is already in the CRM before Create a Contact adds a card. The same pairing works for accounts with Search Companies and Create a Company, which keeps duplicates out.

Invoices your bookkeeper can follow. Watch Invoices passes each invoice event to a finance sheet or chat channel. Know what the list lacks: no module updates an invoice, and according to the Make documentation the app is unavailable in 15 countries, including the Russian Federation, Ukraine and Kazakhstan. For anything the modules skip, Make an API Call reaches the Bitrix24 API with the same connection.

New to the editor? The Make training starts from zero, and Make pricing explains how operations are counted on your plan. If you are also weighing n8n, the n8n vs Make comparison puts both tools side by side.

Connect

How do you connect Bitrix24 to Make?

  1. 01

    Add a Bitrix24 module

    In your scenario, click the +, search for Bitrix24 and pick any module, Watch Deals for instance. Then click Create a connection. A connection is your Bitrix24 account linked to Make once and reused by every Bitrix24 module afterwards.

  2. 02

    Name the connection

    Give the connection a name you will recognize later, such as the team or the portal it belongs to. This step is optional, yet it saves confusion the day you link a second Bitrix24 account.

  3. 03

    Authorize Make and save

    Make opens the Bitrix24 authorization page, or asks for the key Bitrix24 gives you. Approve the access, then click Save. Back in the module, Make can now list your Bitrix24 records for you.

First scenario

Your first scenario: a ready-made task for each deal event

GoalWhen the deal event you pick happens in Bitrix24, Make creates a task and adds a checklist to it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Search for Bitrix24, choose Watch Deals and link your account with Create a connection.

  2. 02

    Set the trigger

    In Watch Deals, specify the deal event that should start the scenario. Once the connection exists, Make fills the choices for you, so there is nothing to type from memory.

  3. 03

    Add the task

    Click the + to the right of Watch Deals and add Create a Task. Map data from the deal bundle (one bundle is one item passing between modules, here one deal) into the task.

  4. 04

    Attach the checklist

    Add Add a Checklist to a Task after it and point it at the task that Create a Task just returned, so the steps land on the right task.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Open each module to read the bundles it received, then check in Bitrix24 that the task and its checklist are there.

  6. 06

    Schedule and switch on

    Open the clock on Watch Deals: a new scenario runs every 15 minutes by default, the shortest interval on the Free plan. Switch the scenario on and it keeps watching your deals.

Triggers

Which Bitrix24 events can start a scenario?

6 modules start a scenario when something happens in Bitrix24. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Bitrix24 as soon as it happens.

Bitrix241Watch Contacts

Watch Contacts

Scheduled trigger

In Make“Triggers when a contact is created or modified.”

Watch Contacts brings each contact created or edited in Bitrix24 into your scenario, one bundle per contact, so your other tools learn about the change without anyone retyping it.

How it fires
scheduled. Make checks Bitrix24 on the scenario's schedule, every 15 minutes by default, and hands over what it finds at that check.
When to use it
copy fresh contacts to your mailing tool or a shared sheet after sales adds or corrects a card.
Watch out
edits fire it as well as creations, so the same person can come through again; the next module should update the copy rather than add a second one.
Bitrix242Watch Companies

Watch Companies

Scheduled trigger

In Make“Triggers when a company is created or modified.”

Every company created or modified in your CRM reaches the scenario through Watch Companies, which gives account-level automations a clear starting point.

How it fires
scheduled. Make polls Bitrix24 at the interval set on the scenario's clock, never faster than 15 minutes on the Free plan and down to 1 minute on paid plans.
When to use it
a new client company should get its own folder or project in the tool your delivery team uses.
Watch out
a simple edit to the company fires it too, so make the next step check whether the folder already exists before creating another one.
Bitrix243Watch Leads

Watch Leads

Scheduled trigger

In Make“Triggers when the specified event occurs on leads.”

With Watch Leads, a lead event you specify in Bitrix24 becomes the start of a scenario, so incoming prospects get routed while they are still warm.

How it fires
scheduled. Make asks Bitrix24 for matching lead events on each run of the scenario's schedule; nothing reaches Make between two checks.
When to use it
post new prospects in the sales chat channel, or open a first-call task for the person on duty.
Watch out
the module follows only the event you specified. Try it with Run once on a real lead to confirm that event is the one your team actually produces.
Bitrix244Watch Deals

Watch Deals

Scheduled trigger

In Make“Triggers when the specified event occurs on deals.”

Watch Deals turns movement in your pipeline into automation: when the deal event you picked happens, the deal enters the scenario as a bundle ready to map.

How it fires
scheduled. Make checks Bitrix24 on the scenario's schedule, 15 minutes by default, rather than waiting for Bitrix24 to call it.
When to use it
brief the delivery team, or prepare the onboarding tasks, when a deal reaches the event that matters to you.
Watch out
a deal changed right after a check waits for the next run. Tell the sales team before they expect an instant alert.
Bitrix245Watch Invoices

Watch Invoices

Scheduled trigger

In Make“Triggers when the specified event occurs on invoices.”

Finance sees what sales bills: Watch Invoices feeds each invoice event you select into the scenario, so the figures leave Bitrix24 without a manual export.

How it fires
scheduled. At every scheduled run, Make reads Bitrix24 and passes on one bundle per invoice it finds.
When to use it
send invoice details to a bookkeeping spreadsheet or warn the finance channel when an invoice event occurs.
Watch out
no listed module can update an invoice afterwards. If your scenario must change one, plan a Make an API Call module and the Bitrix24 API documentation.
Bitrix246Watch Tasks

Watch Tasks

Scheduled trigger

In Make“Triggers when the specified event occurs on tasks.”

Watch Tasks lets a task event in Bitrix24 kick off work elsewhere, like telling a client or a manager that a job has moved on.

How it fires
scheduled. Make queries Bitrix24 on the rhythm set in the scenario's scheduling, every 15 minutes unless you change it.
When to use it
log task events in a time sheet, or ping a manager in chat when the event you chose happens.
Watch out
each task found runs the next modules, and every module run on a bundle is one operation, the unit Make counts on your plan. A busy board uses more of it than a quiet one.
Modules

What else can Bitrix24 do in Make?

Bitrix24 gives you 31 modules in 7 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Contact

5 modules

You can watch, create, update, search, retrieve, and delete the contacts using the following modules.

Bitrix241

Search Contacts

Search

In Make“Searches for contacts selected by the filter specified as the parameter.”

Search Contacts looks through your Bitrix24 contacts with a filter you set and returns every match, the safest way to find out whether someone is already on file.

When to use it
before turning a form entry into a contact, so the same person does not end up with two cards.
Watch out
a search can return zero, one or many bundles, and each one runs the modules after it; narrow the filter when you expect a single person.
Bitrix242

Get a Contact

Action

In Make“Returns a contact by the specified contact ID.”

When you already hold a contact ID, Get a Contact fetches that exact card as it stands now, so later modules work from fresh values instead of stale ones.

When to use it
another module hands you a contact ID and you need the full card before writing to that person.
Watch out
it works with the ID only; if all you have is a name, start with Search Contacts.
Bitrix243

Create a Contact

Action

In Make“Creates a new contact.”

Create a Contact adds a new person to Bitrix24 from whatever the previous module delivers: a sign-up, a spreadsheet row, an event registration.

When to use it
every webinar or newsletter sign-up should become a CRM contact the sales team can call.
Watch out
if the same person may sign up twice, run Search Contacts first, otherwise you risk two cards for one customer.
Bitrix244

Update a Contact

Action

In Make“Updates an existing contact.”

Update a Contact changes an existing Bitrix24 contact with the values you map, so a detail corrected in your support or billing tool also lands in the CRM.

When to use it
a customer fixes their details in a ticket and sales should see the new version.
Watch out
it acts on a contact that already exists, so feed it the one found by Search Contacts or received from Watch Contacts.
Bitrix245

Delete a Contact

Action

In Make“Deletes a contact.”

Delete a Contact removes a contact from Bitrix24 for good, which helps you honor removal requests or clear the test records your scenarios left behind.

When to use it
a person asks to be forgotten in your form tool and the CRM card has to go too.
Watch out
a deletion cannot be undone from Make; try it with Run once on a dummy contact before switching the scenario on.

Company

5 modules

You can watch, create, update, search, retrieve, and delete the companies.

Bitrix246

Search Companies

Search

In Make“Searches for companies selected by the filter specified as the parameter.”

Need the account behind a name? Search Companies filters your Bitrix24 companies and hands back each one that matches, ready to be linked or reused.

When to use it
before creating a company from a signed contract, to skip accounts already in the CRM.
Watch out
if several companies match, the rest of the scenario runs once per company; tighten the filter so a single account comes back.
Bitrix247

Get a Company

Action

In Make“Returns a company by the specified company ID.”

Get a Company returns one company record from Bitrix24 by its ID, handy when an earlier step only carries that reference and you need the whole account.

When to use it
preparing a quote or a welcome pack that needs the company's details gathered in one place.
Watch out
it expects an ID coming from a previous module, such as Watch Companies or Search Companies, never a name typed by hand.
Bitrix248

Create a Company

Action

In Make“Creates a new company.”

Create a Company opens a new account in Bitrix24, so a customer won in another tool shows up in the CRM with its own record.

When to use it
a contract signed in your e-signature tool, or a new customer in your billing app, should create the company without anyone typing it.
Watch out
two sources feeding the same customer will create two accounts; search with Search Companies before this module.
Bitrix249

Update a Company

Action

In Make“Updates an existing company.”

Update a Company keeps an account current: the values you map from another module replace the ones stored on that Bitrix24 company.

When to use it
a customer's details change in your accounting tool and the sales team should work from the new version.
Watch out
run it once with Run once on a single company and open that record in Bitrix24 to confirm the right account changed.
Bitrix2410

Delete a Company

Action

In Make“Deletes a company.”

Delete a Company erases an account from your Bitrix24 CRM, useful for tidying up duplicates once their useful data has been copied elsewhere.

When to use it
Search Companies spotted a duplicate account and the extra record should disappear.
Watch out
Make cannot bring a deleted company back, so add a check before this module and let only the intended record reach it.

Lead

5 modules

You can watch, create, update, search, retrieve, and delete the leads using the following modules.

Bitrix2411

Search Leads

Search

In Make“Searches for leads selected by the filter specified as the parameter.”

Search Leads scans your Bitrix24 leads with the filter you define and returns those that fit, each as its own bundle.

When to use it
a prospect writes in again and you want to reuse the existing lead instead of opening a new one.
Watch out
no match is a normal result, not an error, so decide what the scenario should do for a brand new prospect.
Bitrix2412

Get a Lead

Action

In Make“Return a lead by the specific lead ID.”

Get a Lead retrieves a single lead from Bitrix24 using its ID and gives the following modules its latest content.

When to use it
a message or a task references a lead and you want the whole record before scoring or routing it.
Watch out
this is a lookup by ID only, so keep the lead ID whenever an earlier module returns it.
Bitrix2413

Create a Lead

Action

In Make“Creates a new lead.”

Create a Lead drops a new prospect into Bitrix24 from outside, whether it comes from an ad form, a chatbot or a spreadsheet of trade show contacts.

When to use it
marketing collects contacts in a tool Bitrix24 does not read, and sales should see them as leads.
Watch out
each bundle creates one lead, so a list of rows produces just as many leads; check the list before running the scenario on it.
Bitrix2414

Update a Lead

Action

In Make“Updates a new lead.”

Update a Lead moves an existing lead forward with values from another module, so what happens outside Bitrix24 shows up on the lead card.

When to use it
a prospect books a meeting in your calendar tool and the lead should reflect it.
Watch out
it is meant for a lead that already exists; when the lead may be missing, start the branch with Search Leads.
Bitrix2415

Delete a Lead

Action

In Make“Deletes a lead.”

Delete a Lead permanently removes a lead, keeping the pipeline free of spam entries and of the test data your scenarios created.

When to use it
a lead marked as spam or as a duplicate should vanish from Bitrix24.
Watch out
there is no undo from Make, so run it on test leads first and keep it behind a careful check.

Deal

5 modules

You can watch, create, update, retrieve, search, and delete the deals using the following modules.

Bitrix2416

Search Deals

Search

In Make“Searches for deals selected by the filter specified as the parameter.”

Search Deals queries your Bitrix24 pipeline with a filter and returns every deal that matches, ready for a report or a grouped follow-up.

When to use it
gathering the deals of one company before sending a summary to the account manager.
Watch out
a broad filter can return many deals, and each bundle costs operations in every module that follows.
Bitrix2417

Get a Deal

Action

In Make“Returns a deal by the specified deal ID.”

Get a Deal pulls the current state of one deal from Bitrix24 by its ID, useful when another step only holds the reference.

When to use it
a module hands you a deal ID and you want the full deal before notifying the sales rep.
Watch out
it needs the deal ID from a previous module; a deal name will not work here, Search Deals handles that case.
Bitrix2418

Create a Deal

Action

In Make“Creates a new deal.”

Create a Deal opens a new opportunity in Bitrix24 from an event elsewhere, so a quote request or an order becomes pipeline without manual entry.

When to use it
a quote form on your site should give sales a deal to work on, not an email to forward.
Watch out
if the same request can arrive twice, check with Search Deals first so the opportunity does not appear twice.
Bitrix2419

Update a Deal

Action

In Make“Updates an existing deal.”

Update a Deal changes an existing deal with values mapped from another app, so a payment or a signature moves the deal without anyone clicking in Bitrix24.

When to use it
a contract gets signed in your e-signature tool and the deal should show it.
Watch out
two scenarios updating the same deal can overwrite each other; keep one scenario in charge of each change.
Bitrix2420

Delete a Deal

Action

In Make“Deletes a deal.”

Delete a Deal takes a deal out of Bitrix24 entirely, for example the test opportunities left behind while you were building scenarios.

When to use it
cleaning duplicates found by Search Deals or removing a deal created by mistake.
Watch out
once deleted, the deal is gone; try the module with Run once on a test deal before trusting it with real data.

Invoice

4 modules

You can watch, create, search, retrieve, and delete the invoices from the following modules.

Bitrix2421

Search Invoices

Search

In Make“Searches for invoices selected by the filter specified as the parameter.”

Search Invoices finds the Bitrix24 invoices that meet your filter and hands them to the scenario one by one, a quick base for payment follow-ups.

When to use it
listing a customer's invoices before a call between sales and finance.
Watch out
this module reads invoices, it does not change them, and the list has no update module for invoices.
Bitrix2422

Get an Invoice

Action

In Make“Return an invoice by the specific invoice ID.”

Get an Invoice returns one invoice from Bitrix24 through its ID, so you can pass its details to accounting or to the customer.

When to use it
Watch Invoices gave you an invoice and a later step needs the complete record.
Watch out
keep the ID from the earlier module, because this one does not search; for that, use Search Invoices.
Bitrix2423

Create an Invoice

Action

In Make“Creates a new invoice”

Create an Invoice issues a new invoice in Bitrix24 from the data in your scenario, so an order recorded elsewhere does not get typed twice.

When to use it
an order closed in your shop or booking tool should produce the invoice in the CRM.
Watch out
no listed module edits an invoice afterwards, so check the mapped values with Run once before activating.
Bitrix2424

Delete an Invoice

Action

In Make“Deletes an invoice.”

Delete an Invoice removes an invoice from Bitrix24, mostly to clean up the test invoices a scenario created while you were building it.

When to use it
a scenario run created the same invoice twice and the extra copy must go.
Watch out
with no update module, deleting and recreating is tempting; think twice, a removed invoice cannot be restored from Make.

Task

6 modules

You can watch, create, update, search, retrieve, and delete the task using the followig modules.

Bitrix2425

Search Tasks

Search

In Make“Searches for tasks selected by the filter specified as the parameter.”

Search Tasks lists the Bitrix24 tasks that match your filter, giving you a batch to report on or to chase.

When to use it
sending a manager the tasks tied to one project or one person before a review meeting.
Watch out
several matches mean several bundles; for one message listing them all, add an aggregator, the module that groups bundles into one.
Bitrix2426

Get a Task

Action

In Make“Returns a task by the specific task ID.”

Get a Task reads one task from Bitrix24 by its ID and hands its current content to the next module.

When to use it
a chat message or a form carries a task reference and you want the details before replying.
Watch out
the ID must come from Bitrix24 itself, through Watch Tasks, Search Tasks or Create a Task.
Bitrix2427

Create a Task

Action

In Make“Creates a new task.”

Create a Task assigns work in Bitrix24 from any event the scenario receives, so nothing depends on someone remembering to open the CRM.

When to use it
a new deal, a support ticket or a signed contract should give a colleague a concrete to-do.
Watch out
follow it with Add a Checklist to a Task when the job has several steps, rather than packing them into one text.
Bitrix2428

Update a Task

Action

In Make“Updates an existing task.”

Update a Task edits an existing Bitrix24 task with values from another module, keeping the task board in line with what happens outside it.

When to use it
a client approves a delivery in another tool and the related task should reflect that.
Watch out
if the same scenario also uses Watch Tasks, the change you make can be picked up again at the next check; make sure it does not feed itself.
Bitrix2429

Delete a Task

Action

In Make“Deletes a task.”

Delete a Task wipes a task from Bitrix24, for instance the tasks a scenario generated for a deal that was later cancelled.

When to use it
removing duplicate tasks or the ones created while you were testing.
Watch out
the deletion is final from Make's side, so rehearse on a throwaway task before real ones go through.
Bitrix2430

Add a Checklist to a Task

Action

In Make“Adds a checklist to an existing task.”

Add a Checklist to a Task attaches a checklist to a task that already exists, so the person in charge sees every step to tick off.

When to use it
an onboarding or delivery task always follows the same steps and you want them written out every time.
Watch out
the task must exist first; place this module after Create a Task and point it at the task just created.

Others

1 module

You can call APIs using the following module.

Bitrix2431

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Bitrix24 API with the connection you already set up, covering what the listed modules leave out.

When to use it
updating an invoice, or any other Bitrix24 action that has no module of its own.
Watch out
here you work straight from the Bitrix24 API documentation, so it suits someone comfortable reading endpoints; the Make agency can take it on otherwise.
Need help

Need help automating Bitrix24 with Make?

A person reads every message.

FAQ

Bitrix24 and Make: common questions

01Is the Bitrix24 Make integration free?
Yes, on the Make side: Bitrix24 is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and lift the cap on active scenarios. On the Bitrix24 side, the Make documentation states that the modules require a paid Bitrix24 account.
02What is needed to connect Bitrix24 to Make?
A Make account and a paid Bitrix24 account, since the Make documentation says the modules only work with a paid Bitrix24 plan. The app is also unavailable in 15 countries, including Armenia, Moldova, Tajikistan and Uzbekistan. The documentation gives no Bitrix24-specific steps, so the generic ones apply: add any Bitrix24 module, click Create a connection, authorize Make on the Bitrix24 page or paste the key it provides, then click Save. Every Bitrix24 module then reuses that connection.
03Do the Bitrix24 Make integration triggers fire instantly?
No. All 6 Bitrix24 triggers are scheduled: Make checks Bitrix24 on the scenario's schedule instead of being called by Bitrix24 through a webhook. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. A deal changed just after a check therefore appears at the next run. For sales alerts, choose the interval with that delay in mind and say so to the team.
04What if a Bitrix24 module is missing in Make?
Use Make an API Call. It calls any endpoint of the Bitrix24 API with the connection you already have, so it covers what the 37 listed modules do not, such as updating an invoice, which has no dedicated module. You will need the Bitrix24 API documentation to pick the right endpoint. If the blocker is geographic, no module changes it: the Make documentation lists 15 countries where the Bitrix24 app is not available, including Belarus, Georgia and Kyrgyzstan.
05Should Bitrix24 be automated with Make or n8n?
It depends on your criteria rather than on a winner. On Make, Bitrix24 comes with 37 ready modules for contacts, companies, leads, deals, invoices and tasks, plus Make an API Call for the rest, and all its triggers are scheduled. The same app often has an n8n node too. Compare what each tool offers for the records you actually automate, where your other apps already connect, and which editor your team finds easier to read. The comparison linked higher on this page walks through both.
Same platform

Other docs you might need on this stack.

Browse all integrations