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 file uploads, groups, metadata, webhooks, conversions, and addons within n8n workflows. It supports a wide range of operations such as uploading files from various sources, managing stored files and groups, handling metadata, working with webhooks, performing file conversions, and executing or checking the status of Uploadcare addons.
The addonExecutionStatus operation specifically allows users to check the execution status of a previously triggered addon by providing the addon name and a request ID. This is useful for monitoring asynchronous addon processes and integrating their results into automated workflows.
Practical examples:
- Automatically upload images or documents from URLs or binary data in workflows.
- Manage file groups and metadata for organizing uploaded content.
- Trigger and monitor custom Uploadcare addons to process files (e.g., image transformations, virus scanning).
- Use webhook management to react to Uploadcare events.
- Check the status of an addon execution to proceed only after processing completes.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform on Uploadcare (e.g., uploadFile, executeAddon, addonExecutionStatus). |
| Addon Name | The name of the addon to execute or check status for (used in executeAddon and addonExecutionStatus). |
| Request ID | The unique identifier of the addon execution request to check its status (used in addonExecutionStatus). |
Note: The node supports many other properties depending on the selected operation, but for the addonExecutionStatus operation, only "Addon Name" and "Request ID" are relevant.
Output
The node outputs the JSON response returned by the Uploadcare API for the selected operation inside the json field of each item.
For the addonExecutionStatus operation, the output JSON contains the status details of the specified addon execution request, which typically includes information such as current state, progress, results, or errors related to that addon run.
The node does not output binary data for this operation.
Dependencies
- Requires an Uploadcare API credential with a public key and private key configured in n8n.
- Uses the official Uploadcare JavaScript SDK packages (
@uploadcare/upload-clientand@uploadcare/rest-client) bundled within the node. - No additional external dependencies beyond the Uploadcare service and valid credentials.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing incorrect addon names or request IDs may result in errors or empty responses.
- Network connectivity problems can prevent communication with the Uploadcare API.
Error messages:
"Unknown operation": Occurs if an unsupported operation value is provided; ensure the operation is one of the supported options.- Authentication errors: Verify that the API keys are correctly set up and have sufficient permissions.
- Not found or invalid request ID errors: Confirm the request ID corresponds to a valid addon execution.
Resolution tips:
- Double-check all input parameters for typos or incorrect values.
- Ensure the Uploadcare API keys are active and correctly linked in n8n credentials.
- Review Uploadcare API documentation for addon usage and request ID generation.