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
The node integrates with the Uploadcare API, providing a wide range of file and group management operations. Specifically, the storeFile operation marks a previously uploaded file as stored (i.e., makes it permanent in Uploadcare storage). This is useful when you want to ensure that a file remains available and is not automatically deleted after a temporary period.
Common scenarios for using the storeFile operation include:
- Finalizing files after upload to prevent automatic cleanup.
- Managing file lifecycle by explicitly storing files once they are confirmed for use.
- Integrating with workflows where files are uploaded temporarily and then selectively stored based on business logic.
Example: After uploading a file via Uploadcare, you can use this node operation to store the file permanently by providing its UUID.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier of the file or group to operate on. For the storeFile operation, this is the UUID of the file you want to mark as stored. |
Output
The output JSON contains the response from the Uploadcare API related to the storeFile operation. Typically, this includes metadata about the stored file such as its UUID, status, and other file details confirming that the file has been successfully stored.
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 setup.
Troubleshooting
- Invalid UUID: If the provided UUID does not correspond to an existing file, the API will return an error. Verify the UUID is correct and corresponds to a valid uploaded file.
- Authentication errors: Ensure the API keys are correctly set up and have sufficient permissions.
- Unknown operation error: This occurs if the operation parameter is incorrect or missing; ensure "storeFile" is selected.
- Network issues: Connectivity problems with Uploadcare API endpoints may cause timeouts or failures.