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. Specifically for the uploadMultipart operation, it uploads a file in multiple parts, which is useful for handling large files or unstable network conditions by splitting the upload into smaller chunks.
Common scenarios where this node is beneficial include:
- Uploading large media files (videos, high-resolution images) to Uploadcare.
- Automating file uploads from binary data within n8n workflows.
- Managing files and metadata on Uploadcare programmatically.
Practical example:
- A user has a workflow that processes images and needs to upload them to Uploadcare in chunks to ensure reliability and resume capability. The
uploadMultipartoperation allows uploading these files efficiently.
Properties
| Name | Meaning |
|---|---|
| Binary Property | Name of the binary property containing the file to upload. Default is "data". |
| File Name | Optional custom name for the uploaded file. If not provided, the original binary filename or "file" is used. |
Output
The node outputs a JSON object representing the response from the Uploadcare API after the multipart upload completes. This typically includes details about the uploaded file such as its UUID, URL, size, and other metadata returned by Uploadcare.
If the node supports binary data output, it is not explicitly handled here; the output focuses on 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 SDK packages (
@uploadcare/upload-clientand@uploadcare/rest-client). - The node expects binary data input available in the specified binary property within the incoming items.
Troubleshooting
- Missing or invalid credentials: Ensure the Uploadcare API keys are correctly configured in n8n credentials.
- Binary property not found: Verify that the binary property name matches the actual binary data property in the input item.
- File name issues: If no file name is provided and the binary data lacks a filename, the node defaults to
"file", which might cause confusion if multiple files have the same default name. - Large file upload failures: Multipart upload helps mitigate this, but network interruptions or API limits may still cause errors. Check Uploadcare API limits and retry logic.
- Unknown operation error: Occurs if the operation parameter is incorrect or unsupported; ensure the operation is set to
"uploadMultipart"for this use case.