Actions290
- Task Actions
- Direct API Actions
- CRM Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Get Entity
- Add Entity
- Update Entity
- Delete Entity
- Get Entity Rights
- Get Entity Sections
- Add Entity Section
- Update Entity Section
- Delete Entity Section
- Get Entity Item
- Add Entity Item
- Update Entity Item
- Delete Entity Item
- Get Entity Item Properties
- Add Entity Item Property
- Update Entity Item Property
- Delete Entity Item Property
- Chat Actions
- User Field Actions
- File Actions
- User Field Config Actions
- Duplicate Actions
- Timeline Actions
- Disk Actions
- Upload File
- Download File
- Delete File
- Get File Info
- List Files
- Create Folder
- Delete Folder
- Get Storage Info
- Get Storages
- Get Storage
- Get Folders
- Get Folder
- Add Folder
- Update Folder
- Copy Folder
- Move Folder
- Rename Folder
- Get Files
- Get File
- Copy File
- Move File
- Rename File
- Share Item
- Get Shared Items
- Get Sharing Rights
- Update Sharing Rights
- Workflow Actions
- Status Actions
- Calendar Actions
- Chatbot Actions
- Events Actions
- Lists Actions
- Product Actions
- Open Lines Actions
- Telephony Actions
- Register External Call
- Finish External Call
- Hide External Call
- Show External Call
- Search CRM Entities
- Attach Call Record
- Get External Line
- Add External Line
- Update External Line
- Delete External Line
- Get Voximplant Statistics
- Get Voximplant Line
- Get Voximplant SIP Connector
- Get Voximplant SIP Line
- Add Voximplant SIP Line
- Update Voximplant SIP Line
- Delete Voximplant SIP Line
- Message Service Actions
- Notify Actions
Overview
This node interacts with the Bitrix24 platform, specifically providing operations on various resources such as CRM entities and disk storage. For the Disk - List Files operation, it retrieves a list of files from a specified folder in the Bitrix24 disk storage.
Common scenarios where this node is beneficial include:
- Automating file management workflows by listing files in a particular folder.
- Integrating Bitrix24 file storage with other systems or processes.
- Fetching file metadata for reporting or processing purposes.
Practical example:
- You want to retrieve all files stored in a project folder within Bitrix24 to process them further or sync with another cloud storage service.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: β’ OAuth2 (recommended for production) β’ Webhook (simpler but less secure) β’ API Key authentication |
| Folder ID | The unique identifier of the folder in Bitrix24 disk from which to list files. This is required. |
| Return All | Boolean flag indicating whether to return all files or limit the results. If false, only up to the specified maximum pages will be returned. |
| Max pages to load | When "Return All" is false, this limits how many pages of results to fetch. Each page contains up to 50 items. |
| Options | Additional optional parameters: β’ Filter: JSON object specifying filter criteria for files. β’ Order: JSON object specifying sort order of the results. β’ Start: Number indicating start position for pagination. |
Output
The node outputs an array of items where each item represents a file retrieved from the specified folder. Each item's json property contains the file's metadata as returned by the Bitrix24 API.
If binary data output is supported (not explicitly shown in the provided code), it would represent the actual file content; however, based on the static analysis, this operation focuses on listing file metadata only.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Uses Bitrix24 API endpoints internally to fetch file lists.
- No additional external services are required beyond Bitrix24 itself.
- Proper configuration of credentials in n8n is necessary for successful API calls.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Incorrect Folder ID causing empty results or errors.
- Improperly formatted JSON in the "Filter" or "Order" options causing API request failures.
- Pagination limits not set correctly, resulting in incomplete data retrieval.
Error messages:
- Errors thrown by the Bitrix24 API will be surfaced, e.g., "Invalid folder ID" or "Authentication failed".
- If the node is configured to continue on failure, error details will be included in the output JSON under an
errorfield along with resource and timestamp information.
Resolutions:
- Verify and refresh authentication credentials.
- Double-check the Folder ID value.
- Validate JSON syntax in filter/order fields.
- Adjust pagination settings according to expected data volume.