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 wide range of file and media management operations. Specifically for the conversionJobStatus operation, it allows users to check the status of a file conversion job by providing a conversion type and a token associated with that job.
Common scenarios where this node is beneficial include:
- Monitoring the progress of media or document conversions initiated via Uploadcare.
- Automating workflows that depend on the completion of file conversions.
- Integrating Uploadcare's file transformation capabilities into broader automation pipelines.
For example, after starting a file conversion job (e.g., converting an image format), you can use this node with the conversionJobStatus operation to poll the job status until it completes successfully or fails.
Properties
| Name | Meaning |
|---|---|
| Conversion Type | The type of conversion to check the status for. This corresponds to the conversion job type. |
| Conversion Token | The unique token identifying the specific conversion job whose status is being queried. |
Output
The node outputs a JSON object containing the response from the Uploadcare API about the conversion job status. This typically includes details such as whether the job is pending, completed, failed, or in progress, along with any relevant metadata provided by Uploadcare.
No binary data output is produced by this operation.
Dependencies
- Requires an Uploadcare API credential consisting of a public key and a private key.
- Uses the official Uploadcare 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 or missing token: If the conversion token is incorrect or expired, the API will return an error. Ensure the token used matches the one received when initiating the conversion job.
- Incorrect conversion type: Using an unsupported or wrong conversion type may cause the API to reject the request. Verify the conversion type against Uploadcare's supported types.
- API authentication errors: If the API keys are invalid or missing, requests will fail. Confirm that the credentials are correctly set up in n8n.
- Network issues: Connectivity problems can cause timeouts or failures. Check network access to Uploadcare endpoints.