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 supporting operations on various resources including files stored in Bitrix24's disk storage. The "Rename File" operation under the "Disk" resource allows users to rename a file or folder by specifying its unique file ID and the new desired name.
Common scenarios for this node include automating file management tasks within Bitrix24, such as renaming documents or folders based on workflow triggers or external events. For example, after processing a document, you might want to rename it to reflect its updated status or version number automatically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key |
| File ID | The unique identifier of the file or folder to rename |
| New Name | The new name to assign to the specified file or folder |
| Options | Additional optional parameters: - Filter: JSON criteria to filter files (not used here) - Order: JSON sort order (not used here) - Start: Pagination start position (not used here) |
Output
The node outputs an array of items where each item contains a json object representing the result of the rename operation. Typically, this will include confirmation details from Bitrix24 about the renamed file or folder. If an error occurs and the node is configured to continue on failure, the output will contain an error message along with the resource name and a timestamp.
No binary data output is indicated for this operation.
Dependencies
- Requires authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
- Relies on Bitrix24 API endpoints to perform file operations.
- No additional external services are required beyond Bitrix24 itself.
Troubleshooting
Common Issues:
- Invalid or missing File ID: Ensure the File ID corresponds to an existing file or folder in Bitrix24.
- Insufficient permissions: The authenticated user must have rights to rename files in the target Bitrix24 account.
- Network or API errors: Temporary connectivity issues or API rate limits may cause failures.
Error Messages:
- Errors returned from Bitrix24 API will be propagated. If "Continue On Fail" is enabled, these errors appear in the output JSON with an
errorfield describing the issue. - Authentication failures typically indicate invalid or expired credentials; re-authenticate or update credentials accordingly.
- Errors returned from Bitrix24 API will be propagated. If "Continue On Fail" is enabled, these errors appear in the output JSON with an
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 Disk API Methods
- n8n documentation on Creating Custom Nodes