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 (single or groups), retrieve file or group information, manage metadata, handle webhooks, perform file conversions, and execute addons.
The updateMetadata operation specifically updates a metadata key-value pair for a given file or group identified by its UUID. This is useful when you want to add or modify custom metadata associated with your uploaded files, such as tags, descriptions, or other attributes that help organize or describe the content.
Practical example:
You have an image file uploaded to Uploadcare and want to add a "category" metadata key with the value "marketing". Using this operation, you can update the file's metadata to include this information, which can later be used for filtering or searching files.
Properties
| Name | Meaning |
|---|---|
| UUID | File or group UUID to identify the target resource for updating metadata. |
| Metadata Key | The key name of the metadata entry to update or add. |
| Metadata Value | The new value to assign to the specified metadata key. |
Output
The output is a JSON object representing the result of the metadata update operation returned by the Uploadcare API. This typically includes confirmation of the updated metadata or the full metadata object after the update.
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) for API communication. - The node expects these credentials to be configured in n8n under the appropriate credential type.
Troubleshooting
Common issues:
- Invalid or missing UUID: Ensure the UUID corresponds to an existing file or group in Uploadcare.
- Incorrect metadata key or value format: Metadata keys and values should be strings; invalid formats may cause errors.
- Authentication errors: Verify that the API keys are correctly set and have sufficient permissions.
Error messages:
"Unknown operation": This indicates an unsupported operation was requested; ensure the operation parameter is set to"updateMetadata".- API authentication failures: Check that the API keys are valid and properly configured in n8n.
- Metadata update failures: Review the key and value inputs for correctness and ensure the UUID exists.