BitrEx CLI
A PowerShell CLI for safely exporting Bitrix24 companies and contacts to CSV via an inbound webhook
- 1 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Reads and exports personal contact and company CRM data to the local disk
- Export rights equal whatever the inbound webhook was granted
Install
- Services
Manual install
.\run.ps1 export -Webhook "https://your-domain.bitrix24.ru/rest/1/xxxxxxxxxxxxxxxx" -UserId 734Exports the user's companies and their contacts, requires the cloned repo and Windows PowerShell.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads and exports personal contact and company CRM data to the local disk
- Export rights equal whatever the inbound webhook was granted
This is third-party code. Review the repository files before installing.
What it does
A PowerShell script reads Bitrix24 CRM through an inbound webhook with CRM rights and exports companies and their related contacts into companies.csv and contacts.csv, along with an export-summary.json, a data-quality.csv report and an export.log. By default it exports only the current user's companies (by CREATED_BY_ID or ASSIGNED_BY_ID); the contacts-all and export-all commands lift that scope within the webhook's own permissions. It has a dry-run mode that makes no file writes, three request speeds (safe, ultra, fast) with pauses between calls to stay under API limits, and a double-click launcher start-bitrex.cmd with an interactive command picker.
Who it is for. For managers and analysts who need a one-off or regular export of Bitrix24 CRM companies and contacts into CSV.
Good fit when
- You need to export Bitrix24 companies and contacts to CSV for a report or reconciliation
- You need a safe dry-run to check webhook access before a real export
- You need data-quality metrics on the exported records
Not a fit when
- You have no access to Windows PowerShell: the tool targets Windows only
- You need deals, tasks or other CRM entities besides companies and contacts
- You need to write data back to Bitrix24, not just read it
Example request
Export my Bitrix24 companies and their contacts to CSV in safe modeLimitations
Runs only on Windows via PowerShell, there is no cross-platform build. It exports only companies and contacts, not deals or other CRM entities. Requires an inbound webhook with CRM rights, and its secret must never be committed to the repo or to config.json.
How to disable. Delete the project folder and revoke the CRM webhook in your Bitrix24 portal settings.
FAQ
Can I check access before exporting?
Yes, the test command checks the webhook, profile and access to companies and contacts, and sample exports 10 records to check the format.
How do I avoid hitting API rate limits?
Use -Mode safe with 6-14 second pauses between requests, the recommended mode for large exports.
Discussion
No questions or reviews yet.
Related
All Bitrix24 toolsA CLI with full CRUD for Bitrix24 deals, leads, contacts and companies, every command supports --json for agents
Bitrix24 MCP by Bit2Beat
Bitrix24 MCP Server
Bitrix24 MCP server over an inbound webhook: CRM, tasks, disk, calendar, chat, business processes and config migration between portals
MCP server for Bitrix24 CRM analytics: deals, leads, contacts, tasks, manager activity and deals at risk
Bitrix24 MCP with a local CRM cache
bitrix24mcp
A Bitrix24 MCP server that keeps a CRM copy in PostgreSQL or SQLite and answers an agent from cache instead of hitting REST every time
Bitrix24 MCP Server (gunnit)
Bitrix24 MCP Server
A TypeScript MCP server for Bitrix24 CRM: contacts, companies, leads, deals, tasks and sales rep performance reports
Bitrix24 MCP server with sales analytics
Bitrix24 MCP Server
Bitrix24 MCP server in TypeScript with a broad set of CRM tools plus a dedicated group for monitoring manager activity and performance
README in short
The README describes the purpose (exporting companies and contacts via the REST API to CSV and supporting files), requirements (Windows PowerShell, an inbound webhook with CRM rights), the test, sample, export, contacts-all and export-all commands, a full parameter list, three speed modes, the semicolon-delimited CSV format for Russian-locale Excel, dry-run, and a table of common 401, 403 and zero-result errors. It separately spells out security rules: never commit the webhook, config.json or files containing CRM data.