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 grouped), retrieving file or group information, managing metadata, handling webhooks, performing file conversions, and executing addons.
A common use case is automating file uploads and processing in cloud storage, such as uploading user-submitted files, fetching file details for further processing, or managing file metadata programmatically. For example, you could upload images from URLs, retrieve their info to generate thumbnails, or delete files after processing.
Specifically, the fileInfo operation fetches detailed information about a file identified by its UUID, which is useful for obtaining metadata, status, or other attributes of a stored file.
Properties
| Name | Meaning |
|---|---|
| UUID | File or group UUID used to identify the target file or group for operations like fileInfo, storeFile, deleteFile, etc. |
(Note: The full node supports many more properties depending on the selected operation, but for the fileInfo operation only the UUID property is relevant.)
Output
The node outputs an array of JSON objects, each representing the result of the executed operation per input item.
For the fileInfo operation, the output JSON contains detailed information about the specified file, including metadata, status, size, URLs, and other file attributes as returned by the Uploadcare API.
No binary data output is produced by this operation.
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.
Troubleshooting
Common issues:
- Invalid or missing UUID: The operation requires a valid UUID string; providing an empty or incorrect UUID will cause errors.
- Authentication failures: Ensure that the API keys are correctly set up and have sufficient permissions.
- Network or API downtime can cause request failures.
Error messages:
"Unknown operation": Indicates an unsupported or misspelled operation name; verify the operation parameter.- API errors from Uploadcare (e.g., 404 Not Found) typically mean the UUID does not exist or is inaccessible.
Resolutions:
- Double-check the UUID value and ensure it corresponds to an existing file.
- Verify API credentials and permissions.
- Check network connectivity and Uploadcare service status.