Uploadcare API
Actions27
- uploadFile
- uploadFileGroup
- uploadFromUrl
- uploadFromUploaded
- uploadDirect
- uploadMultipart
- fileInfo
- storeFile
- storeFiles
- deleteFile
- deleteFiles
- copyFileToLocalStorage
- copyFileToRemoteStorage
- groupInfo
- deleteGroup
- updateMetadata
- getMetadata
- getMetadataValue
- deleteMetadata
- createWebhook
- updateWebhook
- deleteWebhook
- convert
- conversionJobStatus
- conversionInfo
- executeAddon
- addonExecutionStatus
Overview
This node integrates with the Uploadcare API, providing a comprehensive set of file and group management operations. It allows users to upload files (including multipart and direct uploads), manage file groups, retrieve file information, update metadata, handle webhooks, perform file conversions, and delete files or groups.
The deleteFile operation specifically deletes a file identified by its UUID from the Uploadcare storage. This is useful for cleaning up unused or outdated files programmatically within an automation workflow.
Practical example:
- Automatically delete temporary files after processing them in a workflow to save storage space.
- Remove files that are no longer needed based on certain triggers or conditions in your automation.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier of the file or group to operate on. For the deleteFile operation, this is the UUID of the file to be deleted. |
Output
The output of the deleteFile operation is a JSON object representing the response from the Uploadcare API after attempting to delete the specified file. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
No binary data is output by this operation.
Example output structure (simplified):
{
"status": "success",
"uuid": "file-uuid-deleted"
}
Dependencies
- Requires an API key credential for Uploadcare with both public and private keys.
- Uses the official Uploadcare JavaScript clients (
@uploadcare/upload-clientand@uploadcare/rest-client) internally. - The node expects these credentials to be configured in n8n under a generic API authentication token setup.
Troubleshooting
Common issues:
- Invalid or missing UUID: Ensure the UUID provided corresponds to an existing file.
- Authentication errors: Verify that the API keys are correctly configured and have sufficient permissions.
- Network or API downtime: Check connectivity and Uploadcare service status.
Error messages:
"Unknown operation": Indicates an unsupported operation was requested; ensure the operation parameter is set todeleteFile.- API errors returned from Uploadcare will typically include HTTP status codes and messages; review these to adjust inputs or credentials accordingly.