Overview
This node allows users to interact with the Keepa API, a service that provides detailed product price history and tracking data for Amazon products. The node is designed to send GET requests to Keepa's endpoints, enabling retrieval of various types of data by specifying query parameters.
Common scenarios where this node is beneficial include:
- Fetching historical pricing data for Amazon products to analyze trends.
- Monitoring product availability or sales rank changes over time.
- Integrating Keepa data into workflows for market research or competitive analysis.
For example, a user might configure the node to request price history for a specific ASIN (Amazon Standard Identification Number) by providing appropriate query parameters, then use the output data to trigger alerts or update dashboards.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the type of data to send; currently only "Query" (query parameters) is supported. |
| Query Parameters | Key-value pairs representing the query parameters sent in the GET request to Keepa API. Each pair consists of a key (parameter name) and its corresponding value. |
Output
The node outputs JSON data returned from the Keepa API based on the specified query parameters. This typically includes structured information such as product details, price history arrays, sales ranks, and other metadata provided by Keepa.
If the API returns binary data (not typical for Keepa), it would be available in the binary output field, but this node primarily deals with JSON responses.
Dependencies
- Requires an active internet connection to reach the Keepa API endpoint at
https://api.keepa.com. - Optionally uses an API authentication token (API key) credential configured in n8n to authorize requests to Keepa.
- No additional external dependencies beyond standard HTTP request capabilities.
Troubleshooting
- Missing or invalid API key: If the API key is not provided or incorrect, the Keepa API will reject requests. Ensure the API key credential is correctly set up in n8n.
- Incorrect query parameters: Providing invalid or incomplete query parameters may result in errors or empty responses. Verify parameter names and values against Keepa API documentation.
- Network issues: Connectivity problems can cause request failures. Check network access and proxy settings if applicable.
- Rate limiting: Keepa enforces rate limits; excessive requests may lead to temporary blocking. Implement delays or retries as needed.
Common error messages:
- Unauthorized or 401 errors indicate authentication issues.
- 400-series errors often point to malformed requests or invalid parameters.
- 500-series errors suggest server-side problems; retry later or contact Keepa support.