Actions100
- Activity Actions
- Asset Actions
- Authentication Actions
- Collection Actions
- Extension Actions
- Field Actions
- File Actions
- Folder Actions
- Item Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Setting Actions
- User Actions
- Utility Actions
Overview
This node is designed to delete a file resource by its unique identifier. It is useful in scenarios where you need to programmatically remove files from a system or service, such as cleaning up unused files, managing storage space, or automating file lifecycle management.
For example, if you have a workflow that processes files and then needs to delete them after processing, this node can be used to delete the specified file by providing its ID.
Properties
| Name | Meaning |
|---|---|
| ID | Unique ID of the file object to delete. This is a required string property where you specify the exact identifier of the file you want to remove. |
Output
The output JSON will typically contain information about the result of the delete operation. This may include confirmation of deletion or any metadata returned by the API indicating success or failure. The node does not output binary data.
Dependencies
- Requires an API key or authentication token configured in n8n to authorize requests to the external service managing the files.
- Depends on the external service's API endpoint for deleting files by ID.
Troubleshooting
- Common issues:
- Providing an invalid or non-existent file ID will likely result in an error indicating the file could not be found.
- Missing or incorrect API credentials will cause authentication failures.
- Error messages:
- "File not found" or similar indicates the provided ID does not correspond to any existing file.
- Authentication errors suggest checking the API key or token configuration.
- To resolve these, verify the file ID is correct and ensure valid credentials are set up in n8n.
Links and References
- Refer to the external service's API documentation for file deletion endpoints.
- n8n documentation on setting up API credentials and using HTTP request nodes for custom integrations.