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
The Bitrix24 node allows interaction with the Bitrix24 CRM and business platform. Specifically, for the File resource with the Copy File operation, this node copies a file within the Bitrix24 environment from one folder to another. This is useful when you want to duplicate files for backup, organization, or sharing purposes without altering the original file.
Practical examples include:
- Copying a document from a shared folder to a personal workspace.
- Duplicating marketing materials into different campaign folders.
- Creating backups of important files before making edits.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| Target Folder ID | The ID of the destination folder where the file will be copied. |
| New Name | Optional new name for the copied file. If left empty, the original file name is retained. |
| Folder ID | The ID of the source folder containing the file. Leave empty if the file is in the root folder. |
| File ID | The unique identifier of the file to copy. |
| Options > Access Token | Optional access token string for authentication override. |
Output
The node outputs JSON data representing the result of the copy operation. This typically includes metadata about the newly copied file such as its ID, name, location, and other relevant attributes returned by the Bitrix24 API.
If binary data were involved (e.g., file contents), it would be summarized here, but for the copy operation, the output focuses on JSON metadata only.
Dependencies
- Requires an active connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Proper configuration of credentials in n8n is necessary to authenticate API calls.
- The node relies on Bitrix24's API endpoints to perform file operations.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens can cause authorization failures.
- Incorrect folder or file IDs may lead to "file not found" or "folder not found" errors.
- Insufficient permissions in Bitrix24 to read from the source folder or write to the target folder.
Error messages:
- Errors returned from Bitrix24 API are surfaced in the node output under an
errorfield if "Continue On Fail" is enabled. - Typical error messages include authentication failures, invalid IDs, or permission denials.
- Errors returned from Bitrix24 API are surfaced in the node output under an
Resolutions:
- Verify that the authentication credentials are valid and have not expired.
- Double-check the folder and file IDs for correctness.
- Ensure the authenticated user has appropriate permissions in Bitrix24.
- Use the "New Name" property carefully to avoid naming conflicts.