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 focusing on operations related to the "Disk" resource. The "Get Folder" operation retrieves information about a specific folder in the Bitrix24 disk storage system by its ID. This is useful for workflows that need to access or manipulate files and folders stored within Bitrix24's cloud storage.
Common scenarios include:
- Automating file management tasks such as retrieving folder metadata before uploading or moving files.
- Integrating Bitrix24 disk storage with other systems by fetching folder details.
- Building custom dashboards or reports that require folder information from Bitrix24.
Example: A workflow that triggers when a new folder is created in Bitrix24 and then fetches its details to log or process further.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key. |
| Folder ID | The unique identifier of the folder to retrieve. |
| Options | Additional optional parameters: |
| - Filter | JSON object specifying filter criteria to narrow down results. |
| - Order | JSON object defining the sort order of returned data. |
| - Start | Number indicating the start position for pagination (offset). |
Output
The node outputs an array of items where each item's json property contains the folder data retrieved from Bitrix24. This typically includes folder metadata such as folder ID, name, creation date, modification date, and possibly nested folder or file information depending on the API response.
If the node supports binary data output (not explicitly shown here), it would represent file contents or attachments related to the folder, but this operation primarily returns JSON metadata.
Dependencies
- Requires authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
- Uses Bitrix24 API endpoints internally to fetch folder information.
- 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 missing Folder ID will cause the API call to fail.
- Incorrect authentication setup can lead to authorization errors.
- Network connectivity problems may prevent reaching Bitrix24 API.
- Improperly formatted JSON in filter or order options can cause request failures.
Error messages:
- Errors returned from Bitrix24 API will be included in the output if "Continue On Fail" is enabled.
- Typical error messages include "Folder not found", "Unauthorized", or "Invalid parameter".
Resolutions:
- Verify the Folder ID exists and is accessible with the provided credentials.
- Ensure the selected authentication method is correctly configured and valid.
- Validate JSON syntax in filter and order fields.
- Check network connectivity and Bitrix24 service status.
Links and References
- Bitrix24 Disk API Documentation (official Bitrix24 REST API docs)
- n8n Documentation on Credentials (for setting up API keys and OAuth2)
- Bitrix24 Developer Portal