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 to handle file uploads and management tasks. Specifically, the uploadDirect operation allows users to upload a binary file directly to Uploadcare's storage using the Uploadcare direct upload method. This is useful when you want to send files from n8n workflows to Uploadcare without intermediate steps.
Common scenarios include:
- Uploading user-generated content or files processed in previous workflow steps.
- Automating file storage and management in Uploadcare for websites or applications.
- Integrating Uploadcare as a backend file storage solution within automated workflows.
For example, you might use this node to upload an image file received from a webhook or another service directly into Uploadcare for further processing or delivery.
Properties
| Name | Meaning |
|---|---|
| Binary Property | Name of the binary property that contains the file to upload. Default is "data". |
| File Name | Custom name for the uploaded file (optional). If not set, the original binary filename or "file" is used. |
Output
The node outputs a JSON object representing the response from the Uploadcare API after the direct upload operation. This typically includes metadata about the uploaded file such as its UUID, URL, size, and other relevant details returned by Uploadcare.
No binary data is outputted by this operation; the output is purely JSON metadata describing the uploaded file.
Dependencies
- Requires an API key credential for Uploadcare with both public and private keys.
- Uses the official Uploadcare JavaScript client libraries (
@uploadcare/upload-clientand@uploadcare/rest-client) bundled within the node. - The node expects the input binary data to be available in the specified binary property of the incoming items.
Troubleshooting
- Missing or invalid credentials: Ensure that the Uploadcare API keys are correctly configured in n8n credentials.
- Binary property not found: Verify that the specified binary property exists on the input item and contains valid binary data.
- File name issues: If no file name is provided and the binary data lacks a filename, the node defaults to
"file". Providing a custom file name can avoid confusion. - Unknown operation error: This node supports multiple operations; ensure the operation parameter is set to
"uploadDirect"for this functionality. - API errors: Any Uploadcare API errors will be thrown by the node. Check the error message for details like quota limits, invalid file formats, or network issues.