Overview
This node performs HTTP DELETE requests with flexible data input options. It allows users to send either query parameters or a JSON body as part of the DELETE request. This is useful when interacting with APIs that require DELETE operations with additional data, such as deleting resources conditionally or passing filters.
Common scenarios include:
- Deleting a resource identified by query parameters.
- Sending a JSON payload in the body of a DELETE request for APIs that support it.
- Automating cleanup tasks where specific conditions must be met before deletion.
Example: Deleting a user by ID via query parameter or sending a JSON object specifying multiple IDs to delete.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the type of data to send with the DELETE request. Options: Query (query parameters), JSON (JSON body). |
| Query Parameters | Key-value pairs representing query parameters to append to the URL when Type of Data is 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 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 depends on the API being called but generally includes status information and any returned data from the server.
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 (referred generically as "an API key credential").
- Base URL and headers are preset but can be customized if needed.
Troubleshooting
- Issue: Incorrect or missing query parameters or JSON body keys may cause the API to reject the DELETE request.
- Resolution: Verify that all required keys and values are correctly set according to the target API's specification.
- Issue: Authentication errors if API key or token is missing or invalid.
- Resolution: Ensure proper API credentials are configured in n8n.
- Issue: Unexpected response or empty output.
- Resolution: Check the API documentation to confirm whether the DELETE operation supports the chosen data type (query vs JSON) and adjust accordingly.
- Error Messages: Common HTTP errors like 400 (Bad Request), 401 (Unauthorized), or 404 (Not Found) indicate issues with request formatting, authentication, or resource existence.
Links and References
- HTTP DELETE Method - MDN Web Docs
- REST API Design - Best Practices
- n8n Documentation on HTTP Request Node (for general HTTP method usage)