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 webhook management operations. Specifically for the createWebhook operation, it allows users to create a new webhook in Uploadcare by specifying a target URL and an event type. This is useful for automating workflows that need to respond to Uploadcare events such as file uploads or deletions.
Common scenarios include:
- Automatically triggering downstream processes when a file is uploaded or modified.
- Integrating Uploadcare events with other systems via webhooks.
- Managing webhook lifecycle programmatically within n8n workflows.
Example: Creating a webhook that notifies your application whenever a new file is uploaded to Uploadcare.
Properties
| Name | Meaning |
|---|---|
| Target URL | The URL where the webhook payload will be sent when the specified event occurs. |
| Event | The specific Uploadcare event that triggers the webhook. |
For the createWebhook operation, these two properties are required inputs.
Output
The node outputs a JSON object representing the response from the Uploadcare API after creating the webhook. This typically includes details about the newly created webhook such as its ID, target URL, event type, and status.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for Uploadcare with appropriate permissions.
- Uses Uploadcare's REST client library to interact with the API.
- The node expects the user to configure Uploadcare API credentials in n8n beforehand.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an invalid target URL or unsupported event name may result in API errors.
- Network connectivity problems can prevent successful webhook creation.
Error messages:
"Unknown operation": Indicates the selected operation is not recognized; ensure "createWebhook" is chosen.- API errors returned from Uploadcare (e.g., 400 Bad Request) usually indicate invalid input parameters; verify the target URL and event values.
Resolution tips:
- Double-check API credentials and their permissions.
- Validate the target URL format and ensure it is reachable.
- Confirm the event name matches one supported by Uploadcare webhooks.