Overview
This custom node provides operations on a "Custom Resource" within an external system, specifically supporting a "Delete" operation. The node allows users to delete a specified resource by either selecting it from a list or providing its ID directly. This is useful in workflows where automated cleanup or removal of resources is required, such as deleting obsolete records, removing test data, or managing lifecycle events programmatically.
For example, a user might automate the deletion of a customer record after a certain condition is met or remove outdated entries from a database without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Custom Resource Name or ID | Select a resource from a dynamically loaded list or specify its ID using an expression. |
| Custom Resource ID | The unique identifier of the resource to delete. This field is required when performing the Delete operation. |
Output
The node's output will contain JSON data representing the result of the delete operation. Typically, this includes confirmation of successful deletion or details about the deleted resource. The exact structure depends on the external system's API response but generally confirms whether the resource was removed.
No binary data output is indicated in the provided code.
Dependencies
- The node relies on an external API or service that manages the "Custom Resource".
- It requires an API key or authentication token configured in n8n to authorize requests.
- The
loadOptionsmethod dynamically fetches available models/resources for selection. - The actual execution logic delegates to a router function imported from another module, which handles routing based on the selected operation.
Troubleshooting
- Missing or invalid Custom Resource ID: Since the ID is required for deletion, ensure it is correctly provided; otherwise, the node will likely throw an error.
- Authentication errors: If the API credentials are missing or incorrect, the node will fail to connect to the external service.
- Resource not found: Attempting to delete a non-existent resource may return an error from the API.
- Network issues: Connectivity problems can cause timeouts or failures during the API call.
To resolve these:
- Verify the input fields are correctly set.
- Check API credentials and permissions.
- Confirm the resource exists before attempting deletion.
- Ensure stable network connectivity.
Links and References
- n8n Expressions Documentation
- Refer to the external system's API documentation for details on resource deletion endpoints and expected responses.