Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

This node integrates with the Bitrix24 platform, allowing users to interact with various Bitrix24 resources such as CRM entities and business tools. Specifically, for the Disk resource with the Get Storages operation, it retrieves storage information from Bitrix24's disk service. This is useful for workflows that need to access or manage file storage locations within Bitrix24, such as automating file organization, backup, or synchronization tasks.

Practical examples include:

  • Automatically listing all available storages in a Bitrix24 account to monitor usage.
  • Integrating storage data into reports or dashboards.
  • Triggering further actions based on storage properties or availability.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24:
- OAuth2 (recommended for production)
- Webhook (simpler but less secure)
- API Key authentication
Options Additional parameters to customize the request:
- Filter: JSON object to filter storages by criteria
- Order: JSON object to specify sorting order
- Start: Number indicating the start position for pagination

Output

The node outputs an array of items where each item's json property contains the response data from Bitrix24's disk storage API. The exact structure depends on Bitrix24's API response but generally includes details about each storage such as its ID, type, capacity, and other metadata.

If binary data were involved (e.g., files), it would be included in the binary property of output items, but this operation focuses on metadata retrieval only.

Dependencies

  • Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
  • The node relies on Bitrix24's REST API endpoints for disk storage management.
  • No additional external services are required beyond Bitrix24 itself.
  • Proper configuration of credentials in n8n is necessary for successful API calls.

Troubleshooting

  • Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials or tokens.
  • API call failures: Check network connectivity and Bitrix24 API availability.
  • Invalid filter/order JSON: If using the filter or order options, ensure the JSON syntax is correct and matches Bitrix24 API expectations.
  • Pagination issues: When retrieving large datasets, use the start parameter properly to paginate through results.
  • Error messages: The node returns error details in the output if continueOnFail is enabled; otherwise, it throws exceptions. Review error messages for clues on misconfiguration or API limits.

Links and References

Discussion