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 integrates with the Bitrix24 platform, specifically allowing users to update folder metadata within the Bitrix24 Disk resource. It is useful for automating updates to folder properties such as renaming folders or modifying custom attributes in Bitrix24's cloud storage system.
Typical use cases include:
- Renaming a folder based on workflow conditions.
- Updating folder metadata after file uploads or organizational changes.
- Automating folder property management in Bitrix24 as part of larger CRM or business process automation.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| Folder ID | The unique identifier of the folder to update. |
| Update Data | JSON object containing the fields and values to update on the folder. |
| Options | Additional optional parameters: |
| - Filter | JSON filter criteria (not typically used for update but available). |
| - Order | JSON sort order criteria (not typically used for update but available). |
| - Start | Pagination start position (not typically used for update but available). |
Output
The node outputs an array of items where each item contains a json field representing the response from Bitrix24 after attempting to update the folder. This typically includes updated folder details or error information if the update failed.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error object with keys:
error: Error message string.resource: The resource name ("disk").timestamp: ISO timestamp of when the error occurred.
No binary data output is indicated by the source code.
Dependencies
Requires valid authentication credentials for Bitrix24 via one of these methods:
- OAuth2 token
- Webhook URL
- API key
The node depends on Bitrix24 API endpoints for disk/folder operations.
No additional external libraries beyond those bundled with the node are required.
Proper configuration of credentials in n8n is necessary for successful API calls.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials causing authorization failures.
- Incorrect Folder ID leading to "folder not found" errors.
- Malformed JSON in the "Update Data" property causing request failures.
- Network connectivity issues preventing API communication.
Error messages:
- Errors thrown by the Bitrix24 API will be surfaced in the node output under the
errorfield if "Continue On Fail" is enabled. - Typical errors include authentication failures, invalid folder IDs, or permission denied.
- Errors thrown by the Bitrix24 API will be surfaced in the node output under the
Resolutions:
- Verify and refresh authentication credentials.
- Confirm the Folder ID exists and is accessible.
- Validate JSON syntax in the update data.
- Check network access and proxy settings if applicable.