When Bitrix24 (Alaio) needs to talk to another service, the first idea is usually Zapier — or Make, or a self-hosted tool like n8n. Sometimes that is the right call. Just as often the connector adds a monthly bill, a delivery delay and a third party in the middle of your customer data for something the portal could have done itself. This guide explains how connectors work with Bitrix24, where their hidden costs sit, and which integrations you can run with automation rules alone.
How does Zapier connect to Bitrix24?
Zapier talks to the portal through the REST API, the same interface webhooks use. A zap pairs a trigger — a new lead appeared, a deal changed — with one or more actions in other apps: add a row to a spreadsheet, send a message, create an invoice. Make and n8n follow the same model with different pricing and hosting. The connector is essentially a hosted middleman that polls or receives events from one API and calls another, with a visual editor on top.
What are the hidden costs of a connector?
Four things surface after the trial ends. Per-task billing: every step of every run counts against a monthly quota, so a busy CRM with a few thousand leads a month multiplies into real money — and a retry loop caused by a misconfigured step burns quota on its own. Latency: on lower plans triggers poll on an interval measured in minutes, so a "send the offer immediately" scenario quietly becomes "within a quarter of an hour". Data routing: every contact, deal amount and message body passes through a third party, which procurement and privacy reviews have to sign off. Coverage: a connector exposes the subset of the API its integration author wired up, so the moment you need an uncovered field or method you are back to custom requests anyway.
What can Bitrix24 do without a connector?
More than most teams assume. Automation rules cover the in-CRM part: stage moves, tasks, notifications, field changes — the basics are in the automation rules guide and the workflow guide. What the stock set lacks, Bitrix24 Market robots add as single-purpose steps that run inside the portal: format a phone number, branch on a condition, find a related record, calculate a value. No task quotas, no polling, no data leaving the platform. If the other system only needs to be notified or queried, the integration often collapses into one robot call.
How do I call an external service directly from a workflow?
Two robots replace the typical one-way zap. HTTP request GET/POST sends a request with custom headers and a body — GET, POST, PUT, PATCH, DELETE or HEAD — and returns the status code, response body and a Y/N success flag into the workflow, where Extract value from JSON by path pulls out the fields you need. Build JSON from fields assembles a valid payload from workflow values without hand-escaping quotes. For notifications that must not be lost, Reliable webhook retries failed deliveries on a configurable interval and reports how many attempts it took — a guarantee Zapier only offers through paid replay. These outbound robots run on paid Bitrix24 plans.
When is Zapier still the right choice?
A connector earns its fee when the heavy lifting is on the other side: the target app has a painful OAuth flow you do not want to implement, the scenario chains three or four external SaaS tools with Bitrix24 as just one stop, or the volume is so low that the free tier covers it and nobody on the team wants to see a JSON body. It is also the honest answer when the other service has a polished Zapier integration and no public API documentation worth reading. For everything that starts and ends in the portal — or touches exactly one external endpoint — the in-platform route is cheaper, faster and easier to audit.
Where to go from here
Start by listing your zaps and marking the ones that only move data into or out of Bitrix24 — those are candidates for HTTP request GET/POST or Reliable webhook. The webhooks guide explains inbound and outbound mechanics, and the automation examples collection shows what else runs natively — browse the full robot catalog for the rest.