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 to manage webhooks among many other file and group operations. Specifically, for the updateWebhook operation, it updates an existing webhook's target URL and event type. This is useful when you need to change where Uploadcare sends webhook notifications or modify which events trigger those notifications.
Practical scenarios include:
- Changing the endpoint URL that receives webhook calls after a server migration.
- Updating the event type to listen for different Uploadcare events without recreating the webhook.
Properties
| Name | Meaning |
|---|---|
| Target URL | The URL where the webhook will send its HTTP requests (for createWebhook, updateWebhook, deleteWebhook). |
| Webhook ID | The unique identifier of the webhook to update (required for updateWebhook). |
| Event | The specific webhook event to listen for (e.g., file uploaded) (used in createWebhook and updateWebhook). |
Output
The node outputs a JSON object representing the response from the Uploadcare API after updating the webhook. This typically includes details about the updated 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 communicate with the API.
- The node expects the user to configure the Uploadcare API credentials within n8n.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Webhook ID will cause the update to fail.
- Incorrect or unreachable Target URL may result in webhook delivery failures later.
- Missing required parameters like Webhook ID or Target URL will throw errors.
Error messages:
"Unknown operation": Occurs if the operation parameter is not set to a supported value; ensure "updateWebhook" is selected.- API errors related to authentication indicate invalid or missing API credentials.
- Validation errors from the API if the event or target URL format is incorrect.
To resolve these, verify all input parameters, ensure the webhook exists, and confirm API credentials are valid.