Actions109
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Lists Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Users Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Websites Actions
Overview
This node is designed to delete a specific upload by its ID. It is useful in scenarios where you need to manage and clean up uploaded files or data entries programmatically, such as removing outdated or incorrect uploads from a system.
For example, if you have an automated workflow that processes file uploads and later determines some are no longer needed, this node can be used to delete those uploads by specifying their unique IDs.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the upload to be deleted. This is a required numeric value representing the specific upload entry targeted for deletion. |
Output
The node outputs JSON data indicating the result of the delete operation. Typically, this will include confirmation of successful deletion or details about any errors encountered.
If the node supports binary data output (not evident from the provided code), it would relate to any files or data associated with the upload being deleted, but based on the static analysis, the primary output is JSON status information.
Dependencies
- Requires an API key credential for authentication to the external service managing uploads.
- Needs the base URL of the API endpoint configured in the node credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage for building properties and handling OpenAPI specifications.
Troubleshooting
- Common Issue: Providing an invalid or non-existent upload ID may result in an error or no action taken.
- Resolution: Verify the upload ID exists before attempting deletion.
- Authentication Errors: If the API key or credentials are missing or incorrect, the node will fail to authenticate.
- Resolution: Ensure valid API credentials are configured in n8n.
- Network or API Endpoint Issues: Connectivity problems or incorrect base URL settings can cause failures.
- Resolution: Confirm network access and correct API base URL configuration.
Links and References
- AvantGuard API Documentation (hypothetical link for reference)
- n8n Documentation on Credentials
- OpenAPI Specification