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. It is especially useful for workflows that require uploading files (from binary data or URLs), managing uploaded files and groups, handling metadata, working with webhooks, performing file conversions, and executing add-ons.
For the uploadFile operation specifically, the node uploads a file from binary data available in the workflow to Uploadcare’s storage. This is beneficial when you want to transfer files processed or generated within n8n to Uploadcare for hosting, further processing, or sharing.
Practical example:
You have an automation that generates images or documents, and you want to upload these files to Uploadcare to get a hosted URL for embedding in emails or websites. Using this node’s uploadFile operation, you can directly upload the binary file data from previous nodes.
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 provided, the original binary filename or "file" is used. |
Output
The node outputs a JSON object representing the response from the Uploadcare API after uploading the file. This typically includes details such as the file UUID, CDN URL, size, MIME type, and other metadata returned by Uploadcare.
No binary output is produced by this operation; the output is purely JSON describing the uploaded file.
Dependencies
- Requires an API key credential for Uploadcare with both public and private keys.
- Uses Uploadcare’s official JavaScript SDKs (
@uploadcare/upload-clientand@uploadcare/rest-client) bundled internally. - The node expects binary data to be present on the input items under the specified binary property.
Troubleshooting
- Missing or invalid credentials: Ensure the Uploadcare API keys are correctly configured in n8n credentials.
- Binary data not found: Verify that the input item contains binary data under the specified binary property name.
- Empty or invalid file name: If no file name is provided and the binary data lacks a filename, the node defaults to
"file". Providing a meaningful file name is recommended. - Unknown operation error: This should not occur if the operation is set to
uploadFile. If it does, check the node configuration for typos or unsupported operations.