Fredhopper Product Discovery

Overview

This node integrates with the Fredhopper Product Discovery API, specifically enabling management of catalogs among other resources. The "Create a Catalog" operation allows users to create a new catalog version within a specified tenant and environment. This is useful in scenarios where product data or catalog structures need to be programmatically created or updated as part of an automated workflow.

Practical examples include:

• Automatically creating a new product catalog version when new products are added to an e-commerce platform.
• Integrating catalog creation into CI/CD pipelines for product data updates.
• Managing multiple environments (e.g., test, staging, production) by specifying different tenants and environments.

Properties

Output

The output JSON contains information about the result of the catalog creation request. It includes:

• success: Boolean indicating if the catalog was created successfully.
• message: A descriptive message including the catalog version created.
• catalogVersion: The version identifier of the newly created catalog.
• tenant: The tenant under which the catalog was created.
• environment: The environment context used.
• status: The status of the catalog after creation, typically "inactive" since new catalogs start inactive.
• note: Informational note that new catalogs are inactive by default and require activation.
• response: The raw response object returned from the API call.

Example output snippet:

{
  "success": true,
  "message": "Catalog created successfully with version 1.0.0",
  "catalogVersion": "1.0.0",
  "tenant": "solutions",
  "environment": "cidp-test",
  "status": "inactive",
  "note": "New catalogs are created as inactive. Use 'Activate Catalog' to activate it.",
  "response": { /* full API response */ }
}

Dependencies

• Requires an API key credential for authenticating with the Fredhopper Product Discovery API.
• The node uses Basic Authentication to obtain an OAuth2 bearer token before making API requests.
• The API base URL and credentials must be configured properly in the node's credential settings.
• Network access to the Fredhopper API endpoints (https://items.attraqt.io/catalogs) is required.

Troubleshooting

• Authentication failures: If the node throws errors related to authentication, verify that the API credentials (username, password, auth URL) are correct and have sufficient permissions.
• Invalid catalog data: Ensure the Catalog Data property contains valid JSON matching the expected schema for catalog creation.
• API errors: The node surfaces API error messages; check the message for hints such as invalid parameters or quota limits.
• Inactive catalog after creation: Newly created catalogs are inactive by design. Use the "Activate Catalog" operation to make them active.
• Network issues: Confirm that the n8n instance can reach the Fredhopper API endpoints without firewall or proxy blocking.

Links and References

• Fredhopper Product Discovery API Documentation
• OAuth2 Client Credentials Grant
• n8n HTTP Request Node Documentation (for understanding underlying request mechanics)