Overview
This node performs HTTP DELETE requests with customizable data payloads. It allows users to send either query parameters or a JSON body as part of the DELETE request. This flexibility makes it useful for interacting with APIs that require different ways of passing data when deleting resources.
Common scenarios include:
- Deleting a resource identified by query parameters, such as an ID passed in the URL.
- Sending a JSON object in the body to specify complex deletion criteria or batch deletions.
Practical example:
- Deleting a user by passing their user ID as a query parameter.
- Deleting multiple records by sending a JSON array of IDs in the request body.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the type of data to send with the DELETE request: "Query" (query parameters) or "JSON" (JSON body). |
| Query Parameters | Key-value pairs representing the query parameters to include in the URL when "Type of Data" is set to "Query". Each pair consists of a key and its corresponding value. |
| JSON Object | Key-value pairs representing properties to include in the JSON body when "Type of Data" is set to "JSON". Each pair consists of a key and its corresponding value. |
Output
The node outputs JSON data representing the response from the HTTP DELETE request. The structure of this JSON depends on the API being called but typically includes status information or details about the deleted resource(s).
If the API returns binary data (not indicated here), it would be available in the binary output field, but this node primarily handles JSON responses.
Dependencies
- Requires an active internet connection to perform HTTP requests.
- May require an API authentication token or key configured in n8n credentials to authorize requests against the target API.
- No additional external libraries beyond standard HTTP request handling are needed.
Troubleshooting
- Issue: Incorrect or missing query parameters or JSON body keys can cause the API to reject the DELETE request.
- Resolution: Verify that all required parameters are correctly named and provided according to the target API's specification.
- Issue: Authentication errors if API credentials are not properly configured.
- Resolution: Ensure that the necessary API authentication token or key is set up in n8n credentials and linked to this node.
- Issue: Unexpected response or empty output.
- Resolution: Check the API endpoint URL and ensure the DELETE operation is supported and correctly formed.
- Error Messages: Common HTTP errors like 400 (Bad Request), 401 (Unauthorized), or 404 (Not Found) indicate issues with request formatting, authentication, or resource availability respectively.
Links and References
- HTTP DELETE Method - MDN Web Docs
- REST API Design - Best Practices
- n8n Documentation on HTTP Request Node (for general HTTP operations)