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 provides a comprehensive integration with the Uploadcare API, enabling various file and group management operations within n8n workflows. It supports uploading files (single or groups), retrieving file or group information, storing or deleting files, copying files between local and remote storage, managing metadata, handling webhooks, performing file conversions, and executing addons.
The specific operation copyFileToLocalStorage copies a file identified by its UUID from Uploadcare's storage to local storage managed by Uploadcare. This is useful when you want to ensure a file is stored locally within Uploadcare's infrastructure for faster access or compliance reasons.
Practical example:
- You have a file uploaded via URL or direct upload and want to make sure it is stored locally in Uploadcare for optimized delivery or further processing. Using this operation, you can copy the file to local storage by specifying its UUID.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier of the file or group to operate on. For the copyFileToLocalStorage operation, this is the UUID of the source file to be copied to local storage. |
Output
The node outputs a JSON object representing the result of the copyFileToLocalStorage API call. This typically includes details about the copied file such as its new storage status, UUID, and other metadata returned by Uploadcare.
If the node operation involves binary data (not applicable specifically for copyFileToLocalStorage), the binary output would contain the file content. However, this operation deals with file references and metadata only.
Dependencies
- Requires an API key credential for Uploadcare with both public and private keys.
- Uses the official Uploadcare JavaScript SDK packages (
@uploadcare/upload-clientand@uploadcare/rest-client) bundled within the node. - No additional environment variables are needed beyond the API credentials configured in n8n.
Troubleshooting
Common issues:
- Invalid or missing UUID: Ensure the UUID provided corresponds to an existing file in your Uploadcare account.
- Authentication errors: Verify that the API keys are correctly set up and have sufficient permissions.
- Network or API downtime: Check Uploadcare service status if requests fail unexpectedly.
Error messages:
"Unknown operation": This indicates an unsupported operation was requested; verify the operation parameter is set tocopyFileToLocalStorage.- API errors related to invalid UUID or permissions will be returned from Uploadcare and should be handled accordingly.