Integration of Bitrix24 with Zapier
A marketer wants to automatically create leads from Typeform in B24, a manager — get Slack notifications for new deals, a director — see CRM data in Google Sheets. Each such connection through API is a task for a developer lasting hours. Zapier lets you build an integration in minutes using a visual builder. But the platform has limitations that must be considered when working with Bitrix24.
How Zapier Works with Bitrix24
Zapier interacts with B24 through REST API. Connection is through OAuth: the user authorizes Zapier on their B24 portal. After that, triggers and actions are available.
Available Triggers (B24 events that launch a Zap):
- New lead
- New deal
- New contact / company
- Deal update (stage change)
- New task
Available Actions (what Zapier does in B24):
- Create lead, deal, contact, company
- Update deal (fields, stage)
- Create task
- Add comment to task
- Find contact/company by field (Search action)
Typical Zap Scenarios
Lead Generation
| Source | Zap | Result in B24 |
|---|---|---|
| Typeform | New response → create lead | Lead with form data |
| Calendly | New meeting → create deal | Deal + calendar event |
| Stripe | New payment → update deal | Stage "Paid", amount |
| Mailchimp | New subscriber → create contact | Contact with "Newsletter" tag |
| HubSpot | New contact → create contact in B24 | Database migration |
Notifications and Reports
- New deal in B24 → Slack channel message
- Deal moved to "Lost" stage → Google Sheets row + email to manager
- New lead → SMS to manager via Twilio
- Overdue task → Microsoft Teams notification
Multi-Step Zaps
Zapier supports action chains. Example scenario "new customer":
- Trigger: new deal in B24 with stage "New".
- Search: find contact in Google Contacts by email.
- Branching (Filter): if contact not found — create, if found — update.
- Action: add row to Google Sheets with deal data.
- Action: send welcome email via Gmail.
Multi-step Zaps are available on paid Zapier plans. Each step is one "task" counted in plan limits.
Data Transformation
Between steps, Zapier allows data transformation:
-
Formatter — format dates (YCLIENTS returns
2024-01-15, B24 expects15.01.2024), text transformation (uppercase, trim), math operations - Lookup Table — value mapping: B24 stage code → human-readable name for Slack message
- Code by Zapier — JavaScript or Python for non-standard logic. Example: split full name into last and first name for separate contact fields
Rate Limits and Constraints
Bitrix24 REST API has request limits:
| Parameter | Value |
|---|---|
| Requests per second | 2 (per OAuth token) |
| Requests per hour | Depends on B24 plan |
Batch method (batch) |
Up to 50 commands per request |
Zapier makes requests sequentially. During bulk import (e.g., 500 leads from CSV) the Zap will work slowly — 2 requests per second. For such tasks, direct integration using batch API is better.
Zapier Limitations:
- Polling interval — Zapier checks triggers every 1–15 minutes (depends on plan). For Professional — every 2 minutes, for Free — 15 minutes. Not real-time.
- Instant triggers — B24 supports webhooks, but not all Zapier triggers use them. Check for lightning icon next to trigger — it means instant launch.
- Custom fields — Zapier sees B24 custom fields, but when adding/removing them you need to recreate the connection (Refresh Fields).
- Smart Processes — standard Zapier connector for B24 doesn't support smart processes. For them — Webhooks by Zapier + B24 API directly.
Alternatives to Zapier for B24
| Platform | Advantage over Zapier | Disadvantage |
|---|---|---|
| Albato | Russian platform, ruble pricing, good B24 connector | Fewer Western service connectors |
| Make (Integromat) | More flexible: branching, loops, complex scenarios. Cheaper for high volume | More complex interface |
| n8n | Self-hosted, free, full control | Need server and DevOps |
| Direct Integration | Maximum flexibility and performance | Need developer |
Recommendation: for simple connections (1–3 steps, small volume) Zapier works well. For complex scenarios or high transaction volume — Make or direct integration.
Webhook Integration as Alternative to Connector
If the standard B24 connector in Zapier doesn't support the needed trigger or action:
- In B24, set up outgoing webhook for event (e.g.,
ONCRMLEADADD). - In Zapier, use Webhooks by Zapier → Catch Hook trigger — it accepts arbitrary HTTP requests.
- Webhook data is available in next Zap steps as variables.
For actions: use Webhooks by Zapier → Custom Request — send arbitrary request to B24 REST API with needed parameters.
What We Configure
- Bitrix24 connection to Zapier through OAuth
- Creating and testing Zap scenarios for business tasks
- Mapping CRM fields with external services, including custom fields
- Filter, formatting, and multi-step chain configuration
- Webhook integrations for scenarios not covered by standard connector
- Monitoring and troubleshooting errors in Zap log
- Recommendations for platform choice: Zapier vs Make vs Albato vs direct integration