Overview
This node interacts with the Keepa API, specifically supporting a DELETE operation. It allows users to send DELETE requests to the Keepa service by specifying parameters either as query string arguments or as JSON body data. This flexibility enables users to remove or delete specific resources or data entries managed by Keepa.
Typical use cases include:
- Deleting specific items or records tracked in Keepa by passing identifying parameters.
- Cleaning up or managing data stored in Keepa via automated workflows.
- Integrating Keepa data management into larger automation pipelines where deletion of data is required based on certain conditions.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects how to send the DELETE request data: either as Query Parameters (Query) or as JSON Body (JSON). |
| JSON Object | When Type of Data is set to JSON, this property allows defining multiple key-value pairs that form the JSON body of the DELETE request. Each pair consists of a key (property name) and its corresponding value. |
Output
The node outputs the response from the Keepa API after performing the DELETE request. The output is structured as JSON data under the json field, representing the API's response to the deletion operation. This typically includes status information about the success or failure of the deletion.
If the API returns any binary data (unlikely for a DELETE operation), it would be available in the binary output fields, but this node primarily deals with JSON responses.
Dependencies
- Requires an active connection to the Keepa API endpoint at
https://api.keepa.com. - Optionally uses an API authentication token or key credential configured in n8n to authorize requests to Keepa.
- No additional external dependencies are indicated beyond standard HTTP request capabilities.
Troubleshooting
- Invalid or missing authentication: If the API key or token is not provided or invalid, the API will reject the request. Ensure the API credentials are correctly configured in n8n.
- Incorrect parameter format: When sending JSON data, ensure keys and values are properly defined; malformed JSON bodies can cause request failures.
- Unsupported query parameters: Using unsupported or incorrect query parameters may result in errors or no action taken by the API.
- Network issues: Connectivity problems to the Keepa API endpoint will cause request failures; verify network access.
- API limits or restrictions: Keepa may enforce rate limits or permissions that could block DELETE operations; check API documentation and account status.
Common error messages might include HTTP 401 Unauthorized (authentication issues), HTTP 400 Bad Request (invalid parameters), or HTTP 404 Not Found (resource to delete does not exist).
Links and References
- Keepa API Documentation
- n8n HTTP Request Node Documentation (for understanding underlying request mechanics)