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 users to manage files and groups stored in Uploadcare. The executeAddon operation specifically allows executing an Uploadcare addon on a target file or group identified by its UUID. This is useful for extending file processing capabilities using Uploadcare's addons, such as image transformations, optimizations, or other custom processing workflows.
Practical scenarios include:
- Automatically applying an image optimization addon to newly uploaded images.
- Running a custom addon workflow on specific files or groups to prepare them for delivery.
- Triggering additional processing steps on demand via the addon execution feature.
Properties
| Name | Meaning |
|---|---|
| UUID | File or group UUID that identifies the target on which the addon will be executed. |
| Addon Name | The name of the Uploadcare addon to execute on the specified target (file or group). |
Output
The output JSON contains the response from the Uploadcare API after executing the addon. This typically includes details about the addon execution request, such as status, identifiers, or any returned metadata related to the addon process.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"status": "started",
"requestId": "string",
"addonName": "string",
"target": "uuid"
}
Dependencies
- Requires an Uploadcare API credential consisting of a public key and private key.
- Uses Uploadcare's official JavaScript SDKs (
@uploadcare/upload-clientand@uploadcare/rest-client) to interact with the API. - The node must be configured with valid Uploadcare API credentials in n8n.
Troubleshooting
- Invalid UUID or Addon Name: If the UUID or addon name is incorrect or does not exist, the API call will fail. Verify that the UUID corresponds to an existing file or group and that the addon name is valid.
- Authentication Errors: Ensure that the API keys are correctly set up and have sufficient permissions.
- Unknown Operation Error: This error occurs if the operation parameter is not recognized; ensure it is set exactly to
executeAddon. - API Rate Limits: Uploadcare may enforce rate limits; if exceeded, requests might be rejected temporarily.