Actions20
- Catalog Actions
- Category Tree Actions
- Item Actions
- Locale Actions
Overview
This node integrates with the Fredhopper Product Discovery API to manage category trees among other resources. Specifically, the Get a Category Tree operation retrieves detailed information about a specific category tree by its name and version within a given tenant and environment.
Use cases include:
- Fetching the structure and metadata of a category tree for display or synchronization.
- Integrating category data into other systems or workflows.
- Auditing or verifying category tree versions in different environments.
For example, you might use this node to retrieve the "Spring Collection" category tree version "v2" from your "solutions" tenant in the "cidp-test" environment to update your product catalog UI dynamically.
Properties
| Name | Meaning |
|---|---|
| Tenant | The tenant identifier under which the category tree exists (e.g., "solutions"). |
| Environment | The environment context (e.g., "cidp-test") where the category tree is stored. |
| Category Tree Name | The exact name of the category tree to retrieve. |
| Category Tree Version | The specific version of the category tree to fetch. |
Output
The output is a JSON object representing the requested category tree's full details as returned by the Fredhopper Product Discovery API. This typically includes the hierarchical structure, metadata such as creation and update timestamps, description, and version information.
If the operation succeeds, the node returns an array with one element containing the category tree data.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Fredhopper Product Discovery API.
- The node uses OAuth 2.0 client credentials flow to obtain an access token before making API requests.
- Network connectivity to the Fredhopper API endpoints is necessary.
- Proper configuration of tenant and environment parameters matching the API setup is required.
Troubleshooting
- Authentication failures: If the node cannot obtain an access token, verify that the API credentials (username, password, auth URL) are correct and have sufficient permissions.
- Resource not found errors: Ensure the category tree name and version exist in the specified tenant and environment.
- Invalid parameters: Confirm all required properties (tenant, environment, category tree name, version) are provided and correctly spelled.
- API rate limits or network issues: Check network connectivity and API usage quotas if requests fail intermittently.
- Unexpected response format: If the API changes, the node may fail parsing; updating the node or checking API documentation may be needed.