Actions20
- Catalog Actions
- Category Tree Actions
- Item Actions
- Locale Actions
Overview
This node interacts with the Fredhopper Product Discovery API to manage category trees, among other resources. Specifically, the Update a Category Tree operation allows users to update an existing category tree by providing its name, tenant, environment, and new data. This is useful in scenarios where you need to modify the structure or content of a category tree used for product categorization or navigation in e-commerce or digital catalog systems.
Practical examples include:
- Updating category hierarchies after adding new product categories.
- Correcting or refining category metadata or relationships.
- Synchronizing category trees from external systems into Fredhopper.
Properties
| Name | Meaning |
|---|---|
| Tenant | The tenant identifier (e.g., "solutions") specifying the customer or client context. |
| Environment | The environment name (e.g., "cidp-test") indicating the deployment stage like test or production. |
| FHR Validation | Boolean flag to enable or disable Fredhopper validation on the category tree data. |
| Category Tree Name | The unique name of the category tree to update. |
| Category Tree Data | The JSON string representing the updated category tree structure and content. |
Output
The output is a JSON object representing the response from the Fredhopper API after attempting to update the category tree. It typically contains details about the updated category tree or error information if the update failed.
Example output fields may include:
- Confirmation of the update.
- Updated category tree metadata.
- Any warnings or validation messages returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Fredhopper Product Discovery API.
- The node uses OAuth2 client credentials flow to obtain an access token before making API requests.
- Network connectivity to the Fredhopper API endpoints (
https://items.attraqt.io/category-trees/...). - Proper configuration of tenant and environment parameters matching the Fredhopper setup.
Troubleshooting
- Authentication failures: If the node cannot obtain an access token, check that the API key credential is correctly configured with valid username, password, and authentication URL.
- Invalid category tree name or data: Ensure the category tree name exists and the provided JSON data is well-formed and complies with Fredhopper's expected schema.
- Permission errors: Verify that the API credentials have sufficient permissions to update category trees.
- Network issues: Confirm that the n8n instance can reach the Fredhopper API endpoint without firewall or proxy blocking.
- API errors: The node throws errors if the API returns failure responses; inspect the error message for details and adjust input parameters accordingly.
Links and References
- Fredhopper Product Discovery API Documentation (generic link, replace with actual if available)
- OAuth 2.0 Client Credentials Flow
- n8n HTTP Request Node Documentation (for understanding underlying request mechanics)