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, for the Data Storage > Import operation, it facilitates importing data into Bitrix24 entities such as contacts, deals, leads, companies, quotes, invoices, products, and activities.
This node is beneficial in scenarios where you want to automate the synchronization or migration of data from external systems into Bitrix24. For example, importing a batch of new leads collected from a marketing campaign or updating contact information from an external database.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication. |
| Options | Collection of additional parameters to customize the import operation: |
| - Access Token | The access token string used for authentication (if applicable). |
| - Filter | JSON object specifying filter criteria to select which records to import or process. |
| - Select | Comma-separated list of fields to select during the import operation. |
| - Order | JSON object defining ordering criteria for the imported data. |
| - Start | Number indicating the start position for pagination when importing large datasets. |
Output
- The node outputs an array of items where each item contains a
jsonfield representing the imported data record(s) from Bitrix24. - If an error occurs and "Continue On Fail" is enabled, the output will include an item with an
errormessage, theresourcename, and atimestamp. - The node does not explicitly 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 perform data import operations.
- No additional external services are required beyond Bitrix24 itself.
- Proper configuration of authentication credentials in n8n is necessary.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens can cause authorization failures.
- Incorrect filter or select JSON syntax may lead to API errors.
- Pagination parameters (
start) must be managed carefully to avoid missing or duplicating data. - Network connectivity issues with Bitrix24 API endpoints.
Error Messages:
- Errors returned by Bitrix24 API will be surfaced in the node's output if "Continue On Fail" is enabled.
- Typical messages include authentication failures, invalid parameters, or rate limiting.
Resolutions:
- Verify and refresh authentication credentials.
- Validate JSON syntax for filters and order criteria.
- Adjust pagination parameters according to dataset size.
- Check network connectivity and Bitrix24 service status.