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, the uploadFromUrl operation allows users to upload a file directly from a given URL to Uploadcare's storage. This is useful when you have a publicly accessible file URL and want to import it into your Uploadcare account without downloading and re-uploading manually.
Common scenarios include:
- Importing images or documents hosted on external servers into Uploadcare for further processing or delivery.
- Automating workflows where files are fetched from URLs and stored centrally.
- Using Uploadcare as a CDN or file manager by uploading remote resources seamlessly.
Example: You provide a direct link to an image on the web, specify an optional custom filename, and the node uploads that image to your Uploadcare storage, returning metadata about the uploaded file.
Properties
| Name | Meaning |
|---|---|
| Source URL | The URL of the file to be uploaded from the internet (required for uploadFromUrl). |
| File Name | Optional custom name to assign to the uploaded file. If not provided, original filename or default "file" is used. |
Output
The node outputs JSON data representing the response from the Uploadcare API after uploading the file from the URL. This typically includes metadata such as:
- UUID of the uploaded file
- Original filename or the custom filename if provided
- File size, MIME type, and other attributes
- URLs for accessing the uploaded file
No binary data is output in this operation since the file is uploaded remotely by URL.
Dependencies
- Requires an API key credential for Uploadcare with both public and private keys.
- Uses Uploadcare's official JavaScript SDK packages (
@uploadcare/upload-clientand@uploadcare/rest-client) bundled within the node. - The node must be configured with valid Uploadcare API credentials in n8n.
Troubleshooting
- Invalid URL or inaccessible file: If the source URL is incorrect, private, or blocked, the upload will fail. Ensure the URL is publicly accessible.
- Authentication errors: Missing or invalid API keys will cause authentication failures. Verify credentials are correctly set.
- Unknown operation error: This indicates an unsupported operation was selected; ensure the operation parameter is set to
uploadFromUrl. - Empty or missing Source URL: The node requires a valid URL string; leaving it empty will cause errors.
- Filename conflicts or invalid characters: Custom filenames should be valid and unique to avoid overwriting or errors.