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 URL-based uploads), manage file metadata, copy files between local and remote storage targets, handle groups of files, and work with webhooks and conversion jobs.
The specific operation copyFileToRemoteStorage copies a file identified by its UUID to a specified remote storage target. This is useful when you want to move or replicate files managed by Uploadcare to different remote storage services configured in your Uploadcare account.
Practical example:
You have a file uploaded and stored in Uploadcare, and you want to copy it to a remote cloud storage provider (e.g., Amazon S3, Google Cloud Storage) configured as a remote storage target in Uploadcare. Using this operation, you specify the file's UUID and the target remote storage name to perform the copy.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier of the file or group to operate on. For this operation, it is the UUID of the file to copy. |
| Target | The name of the remote storage target where the file will be copied. |
Output
The output is a JSON object containing the response from the Uploadcare API for the copy operation. This typically includes details about the copied file such as its new location, status, and metadata returned by Uploadcare after the copy completes.
The node does not output binary data for this operation; it only returns JSON metadata about the file copy result.
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. - The user must configure the Uploadcare API credentials in n8n before using this node.
Troubleshooting
Common issues:
- Invalid or missing UUID: Ensure the UUID provided corresponds to an existing file in Uploadcare.
- Incorrect target name: The target must match a remote storage target configured in your Uploadcare account.
- Authentication errors: Verify that the API keys are correct 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; ensure the operation parameter is set correctly.- API errors related to authorization or resource not found will be passed through from Uploadcare; check the error message for specifics and verify credentials and UUIDs.