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 provides integration with the Uploadcare API, enabling a wide range of file and webhook management operations. Specifically for the deleteWebhook operation, it allows users to delete an existing webhook by specifying its target URL. This is useful in scenarios where you want to stop receiving event notifications from Uploadcare for a particular webhook endpoint.
Practical examples include:
- Removing outdated or no longer needed webhooks to reduce unnecessary event traffic.
- Cleaning up webhooks during automation workflows when certain conditions are met.
- Managing webhook lifecycle programmatically within n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Target URL | Webhook target URL to identify which webhook to delete (used in createWebhook, updateWebhook, deleteWebhook) |
Output
The output JSON contains the response from the Uploadcare API after attempting to delete the specified webhook. The exact structure depends on the API's response but typically includes confirmation of deletion or error details.
No binary data output is produced by this operation.
Example output JSON snippet:
{
"result": "success",
"message": "Webhook deleted"
}
(Note: Actual fields depend on Uploadcare API response.)
Dependencies
- Requires an Uploadcare API credential consisting of a public key and a private key.
- Uses Uploadcare's REST client library to perform API calls.
- The node must be configured with valid Uploadcare API credentials in n8n.
Troubleshooting
Common issues:
- Providing an incorrect or non-existent target URL will result in failure to delete the webhook.
- Missing or invalid API credentials will cause authentication errors.
- Network connectivity issues can prevent communication with the Uploadcare API.
Error messages:
"Unknown operation": Indicates that the operation parameter was not set correctly; ensure it is set todeleteWebhook.- API errors related to authorization or resource not found will be returned from Uploadcare and should be checked in the node execution logs.
Resolution tips:
- Verify the target URL exactly matches the webhook you intend to delete.
- Confirm API credentials are correct and have sufficient permissions.
- Check network access and firewall settings if requests fail.