Bitrix24Install

Overview

This node integrates with the Bitrix24 platform, specifically allowing interaction with various Bitrix24 resources such as CRM entities and disk storage. The "Disk" resource with the "Get Storage" operation enables users to retrieve information about a specific storage entity within Bitrix24's file storage system.

Typical use cases include:

• Fetching metadata or details about a particular storage container in Bitrix24.
• Integrating Bitrix24 file storage data into workflows for document management or backup.
• Automating retrieval of storage info to trigger further processing or notifications.

For example, a user might configure this node to get details about a shared drive or folder by specifying its Storage ID, then use that data downstream to list files or manage permissions.

Properties

Output

The node outputs an array of items where each item's json property contains the response data from Bitrix24 related to the requested storage. This typically includes metadata fields describing the storage entity such as its ID, name, type, size, creation date, and other relevant attributes.

If an error occurs and the node is configured to continue on failure, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.

No binary data output is indicated for this operation.

Dependencies

• Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
• The node depends on internal helper functions to make API calls to Bitrix24 endpoints.
• No additional external services beyond Bitrix24 are required.
• Proper configuration of the Bitrix24 credentials in n8n is necessary for successful execution.

Troubleshooting

• Common issues:

  • Invalid or expired authentication credentials leading to authorization errors.
  • Incorrect or non-existent Storage ID causing "not found" errors.
  • Malformed JSON in the filter or order options causing request failures.
  • Network connectivity problems preventing API calls.

• Error messages:

  • Errors thrown by the node will include the message from Bitrix24 API responses.
  • If "continue on fail" is enabled, errors are returned in the output JSON under the error key.

• Resolutions:

  • Verify and refresh authentication credentials.
  • Double-check the Storage ID value for correctness.
  • Validate JSON syntax in filter and order fields before execution.
  • Ensure network access to Bitrix24 API endpoints.

Links and References

• Bitrix24 Official API Documentation
• Bitrix24 Disk API Reference
• n8n Documentation on Credentials