Overview
This node integrates with the Amazon Product Advertising API to retrieve product-related data. Specifically, the "Get Browse Nodes" operation fetches information about Amazon browse nodes, which are categories or subcategories used by Amazon to organize products.
Common scenarios for this node include:
- Enriching product catalogs with category metadata.
- Building navigation trees or filters based on Amazon's browse node hierarchy.
- Analyzing category structures for market research or affiliate marketing.
For example, a user might input a list of browse node IDs to get detailed information about those categories, such as their names and parent-child relationships.
Properties
| Name | Meaning |
|---|---|
| Partner Tag | Amazon Partner Tag used for affiliate tracking; overrides the default if provided. |
| Browse Node IDs (for Get Browse Nodes) | Comma-separated list of Amazon Browse Node IDs to retrieve information for. |
Output
The node outputs an array with one element per input item. Each element contains a json field holding the raw response from the Amazon Product Advertising API for the requested browse nodes.
The structure of the json output corresponds directly to the API's response for browse nodes, typically including details like node names, IDs, ancestors, and children.
No binary data is output by this node.
Dependencies
- Requires an active Amazon Product Advertising API credential with access keys and a partner tag.
- The node depends on the external
amazon-paapilibrary to interact with the Amazon API. - Proper configuration of credentials in n8n is necessary, including Access Key, Secret Key, Marketplace, and Partner Tag.
Troubleshooting
- Missing Partner Tag: If neither the node parameter nor credentials provide a partner tag, the node will throw an error stating that the PartnerTag is required.
- Missing Browse Node IDs: The node requires at least one browse node ID; omitting this will cause an error.
- API Request Errors: Network issues, invalid credentials, or exceeding API rate limits can cause request failures. The node surfaces these errors with messages prefixed by "Failed to execute Amazon PA API operation".
- Invalid Input Format: Ensure that browse node IDs are provided as a comma-separated string without extra spaces or invalid characters.