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. The "Copy Folder" operation under the "Disk" resource allows users to copy a folder from one location to another within their Bitrix24 disk storage.
Typical use cases include automating file management tasks in Bitrix24, such as duplicating project folders, backing up important directories, or organizing files by copying folders into different destination folders programmatically.
For example, a user might automate copying a template folder structure into a new project folder each time a new project is created in Bitrix24.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key. |
| Folder ID | The ID of the source folder that you want to copy. |
| Destination Folder ID | The ID of the target folder where the source folder will be copied to. |
| Options | Additional optional parameters: |
| - Filter | JSON object specifying filter criteria for selecting items (not typically used for copy folder). |
| - Order | JSON object specifying sort order (not typically used for copy folder). |
| - Start | Number indicating start position for pagination (not typically used for copy folder). |
Output
The node outputs an array of items representing the result of the copy operation. Each item contains a json field with details about the copied folder or any error information if the operation failed.
- On success, the output JSON includes metadata about the copied folder.
- On failure, the output JSON includes an
errorfield with the error message, the resource name, and a timestamp.
No binary data output is indicated for this operation.
Dependencies
- Requires authentication credentials for Bitrix24 via OAuth2, webhook URL, or API key.
- Uses Bitrix24 API endpoints internally to perform folder copy operations.
- No additional external services are required beyond Bitrix24 itself.
- Proper configuration of authentication credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing folder IDs can cause errors.
- Insufficient permissions for the authenticated user to access or modify folders.
- Network or API rate limiting issues from Bitrix24.
Error messages:
- Errors returned from Bitrix24 API will be included in the output JSON's
errorfield. - If the node is set to continue on fail, it returns error details instead of stopping execution.
- Errors returned from Bitrix24 API will be included in the output JSON's
Resolutions:
- Verify folder IDs are correct and exist in Bitrix24.
- Ensure the authentication method has sufficient rights.
- Check network connectivity and API limits.
- Use the "continue on fail" option to handle errors gracefully in workflows.