Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
The Bitrix24 node allows users to interact with the Bitrix24 CRM and business platform. Specifically, the Data Storage - Export operation enables exporting data from Bitrix24 resources such as CRM entities. This is useful for scenarios where you want to extract data from Bitrix24 for reporting, backup, integration with other systems, or further processing.
For example, a user might export contact or deal records filtered by specific criteria, select only certain fields, and order the results. This operation supports pagination to handle large datasets efficiently.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
| Options | Collection of optional parameters to customize the export: - Access Token: token string for authentication - Filter: JSON object defining filter criteria to limit exported data - Select: Comma-separated list of fields to include in the output - Order: JSON object specifying sorting order of results - Start: Number indicating the start position for pagination |
Output
The node outputs an array of items where each item contains a json property representing a single exported record from Bitrix24. The structure of each record depends on the selected resource and fields but generally includes the requested fields as key-value pairs.
If an error occurs during execution and "Continue On Fail" is enabled, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
This node does not output binary data.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Uses Bitrix24 REST API endpoints internally to fetch data.
- No additional external dependencies beyond standard HTTP requests to Bitrix24 services.
- Proper configuration of credentials in n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect filter or order JSON syntax causing API request failures.
- Requesting fields that do not exist or are not accessible resulting in empty or partial data.
- Pagination parameters misconfigured, causing incomplete data retrieval.
Error messages:
- Errors returned from Bitrix24 API will be surfaced in the node's output if "Continue On Fail" is enabled.
- Typical messages include authentication failures ("Unauthorized"), invalid parameter formats, or rate limiting notices.
Resolutions:
- Verify and refresh authentication credentials.
- Validate JSON syntax for filter and order properties.
- Confirm field names against Bitrix24 entity definitions.
- Adjust pagination parameters to cover the full dataset.