Fredhopper Product Discovery

Overview

This node integrates with the Fredhopper Product Discovery API, enabling users to manage product catalogs and related resources such as items, category trees, locales, and authentication tokens. Specifically for the Catalog resource with the Default operation (which defaults to listing catalogs), it allows users to list all catalogs or retrieve a subset based on parameters.

Common scenarios where this node is beneficial include:

• Retrieving a list of product catalogs from Fredhopper for synchronization or reporting.
• Managing catalog versions by activating or deleting specific versions.
• Creating new catalogs or querying active catalog versions.

Practical example:

• A user wants to fetch all available catalogs in a given tenant and environment to display them in a dashboard or trigger further processing workflows.

Properties

These properties specify the context (tenant and environment) for catalog operations.

Output

The output is a JSON array containing the response data from the Fredhopper API for the requested catalog operation.

For the listCatalogs operation (the default for Catalog resource):

• Returns an array of catalog objects.
• If the "Simplify Output" option is enabled, each catalog object includes only key summary fields: version, status, created date, updated date, and description.
• Otherwise, the full raw API response is returned.

Example simplified output item:

{
  "version": "1.0",
  "status": "active",
  "created": "2023-01-01T12:00:00Z",
  "updated": "2023-06-01T12:00:00Z",
  "description": "Spring collection"
}

No binary data output is produced by this node.

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 access to the Fredhopper API endpoints (https://items.attraqt.io/catalogs and related URLs) is required.
• No additional external dependencies beyond standard HTTP request capabilities provided by n8n.

Troubleshooting

• Authentication failures:
  Error message: Failed to obtain access token or Authentication failed: ...
  Resolution: Verify that the API credentials (username, password, auth URL) are correct and have sufficient permissions.

• Unsupported operation error:
  Error message: The operation "XYZ" is not supported!
  Resolution: Ensure the selected operation is valid for the Catalog resource. For this node, valid operations include listing, creating, deleting, activating catalogs, etc.

• API request errors:
  Errors may occur due to network issues, invalid parameters, or server-side problems. Check the error message details and verify input parameters like tenant, environment, and catalog version.

• Empty or unexpected output:
  Confirm that the tenant and environment values correspond to existing catalogs in Fredhopper. Also, check if filters like limit or simplify options affect the results.

Links and References

• Fredhopper Product Discovery API Documentation (example placeholder link)
• n8n HTTP Request Node Documentation
• OAuth2 Client Credentials Flow