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 provides a comprehensive integration with the Uploadcare API, enabling various file and group management operations within n8n workflows. Specifically, the uploadFromUploaded operation allows users to take an already uploaded file identified by its UUID and register or process it further via Uploadcare's services.
This node is beneficial in scenarios where files have been previously uploaded to Uploadcare (e.g., via direct upload or other means) and you want to perform additional actions on those files without re-uploading them. For example, you might want to trigger processing, store the file permanently, or use it as part of a larger workflow.
Practical examples include:
- Registering a file that was uploaded outside of n8n for further processing.
- Moving or copying files between storage locations using their UUIDs.
- Managing metadata or triggering conversions on existing files.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier (UUID) of the file or group to operate on. For the uploadFromUploaded operation, this specifies the file UUID that has already been uploaded and will be used as the source for the operation. |
Output
The output of the uploadFromUploaded operation is a JSON object representing the response from the Uploadcare API after processing the specified UUID. This typically includes details about the file such as its status, URLs, metadata, and other relevant information returned by Uploadcare.
If the node supports binary data uploads in other operations, here it deals primarily with JSON responses describing the file state rather than binary content.
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) bundled within the node. - No additional environment variables are required beyond the API credentials configured in n8n.
Troubleshooting
Common issues:
- Providing an invalid or empty UUID will cause the operation to fail because the file cannot be found.
- Missing or incorrect API credentials will result in authentication errors.
- Using the wrong operation name or unsupported parameters may throw an "Unknown operation" error.
Error messages:
"Unknown operation": Indicates the operation parameter is not recognized; ensure the operation is set touploadFromUploaded.- Authentication errors: Check that the API key credentials are correctly configured and valid.
- File not found or invalid UUID errors: Verify the UUID corresponds to an existing uploaded file in your Uploadcare account.