Overview
This node integrates with the Amazon Product Advertising API to retrieve information about Amazon browse nodes. Specifically, the "Get Browse Nodes" operation fetches detailed data about one or more browse nodes identified by their IDs. This is useful for users who want to explore Amazon's product category hierarchy or obtain metadata about specific categories.
Common scenarios include:
- Building a product discovery tool that categorizes items based on Amazon's browse nodes.
- Enhancing affiliate marketing platforms by dynamically retrieving category information.
- Analyzing Amazon's category structure for market research or inventory organization.
Example: Given a list of browse node IDs, the node returns detailed information about each node, such as its name, ancestors, and children nodes.
Properties
| Name | Meaning |
|---|---|
| Partner Tag | Amazon Partner Tag used for affiliate tracking; overrides the default if provided. |
| Browse Node IDs | 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 response from the Amazon Product Advertising API for the requested browse nodes.
The json output includes detailed browse node information such as:
- Node identifiers
- Names
- Ancestor and child nodes
- Other metadata related to the browse node hierarchy
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 it is required.
- Missing Browse Node IDs: The node requires at least one browse node ID; failure to provide these results in an error.
- API Request Errors: Network issues, invalid credentials, or incorrect browse node IDs can cause API request failures. The node logs errors and throws descriptive messages.
- Comma-Separated Input Format: Ensure browse node IDs are correctly formatted as comma-separated strings without extra spaces to avoid parsing issues.