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 manage files within Bitrix24. The "Delete File" operation under the "File" resource enables users to delete a file by specifying its unique file ID. This is useful in automation workflows where files need to be programmatically removed from Bitrix24 storage, such as cleaning up outdated documents, removing temporary uploads, or managing storage quotas.
Practical examples:
- Automatically deleting files after processing them in a workflow.
- Removing obsolete contract files when a deal is closed.
- Cleaning up user-uploaded files after a certain period.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| File ID | The unique identifier of the file to delete. |
| Options | Additional optional parameters: - Access Token: A token string for authentication. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or error details if the operation failed.
If an error occurs and the node is configured to continue on failure, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.
No binary data output is involved in this operation.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- The node depends on Bitrix24's API endpoints for file management.
- Proper configuration of authentication credentials in n8n is necessary.
- Network access to Bitrix24 API endpoints must be available.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect or non-existent File ID causing "file not found" errors.
- Insufficient permissions in Bitrix24 account to delete files.
- Network connectivity problems preventing API calls.
Error messages:
- Errors returned from Bitrix24 API will be included in the output JSON under the
errorfield if "continue on fail" is enabled. - Common error messages may include "Unauthorized", "File not found", or "Access denied".
- Errors returned from Bitrix24 API will be included in the output JSON under the
Resolutions:
- Verify that the authentication method and credentials are correctly set up and valid.
- Confirm the File ID exists and is accessible by the authenticated user.
- Ensure the Bitrix24 user has permission to delete files.
- Check network connectivity and firewall settings.