Fredhopper Product Discovery

Interact with Fredhopper Product Discovery API

Actions20

Overview

The "Upsert Items" operation in the Fredhopper Product Discovery node allows users to create or update product items in a specified tenant and environment via the Fredhopper Product Discovery API. This operation is useful for synchronizing product data from external systems into Fredhopper, ensuring that the product catalog is up-to-date with the latest information.

Typical use cases include:

Importing new product data into Fredhopper.
Updating existing product details such as pricing, descriptions, or availability.
Automating product catalog maintenance workflows by integrating with other systems.

For example, an e-commerce platform can use this node to push updated product information daily to Fredhopper, enabling accurate search and merchandising experiences.

Properties

Name	Meaning
Tenant	The tenant identifier within Fredhopper where the items will be upserted (e.g., "solutions").
Environment	The environment name in Fredhopper (e.g., "cidp-test") where the operation will be performed.
FHR Validation	Boolean flag indicating whether Fredhopper validation should be applied on the data.
Product Data	JSON string containing the product item data to be upserted. This must conform to Fredhopper's expected schema.

Output

The output of the "Upsert Items" operation is a JSON object representing the response from the Fredhopper API after attempting to upsert the items. This typically includes status information about the operation, any errors encountered, and details about the processed items.

Example structure (simplified):

{
  "status": "success",
  "processedItems": [...],
  "errors": [...]
}

No binary data is produced by this operation.

Dependencies

Requires an API key credential for authenticating with the Fredhopper Product Discovery API.
The node performs OAuth2 client credentials authentication by sending a POST request with basic auth headers to obtain an access token before making API calls.
Network connectivity to https://items.attraqt.io endpoints is required.
No additional environment variables are needed beyond the configured API credentials.

Troubleshooting

Authentication failures: If the node throws an error like "Failed to obtain access token" or "Authentication failed", verify that the API credentials (username, password, auth URL) are correct and have sufficient permissions.
Invalid product data: Errors may occur if the Product Data JSON does not conform to the expected schema. Validate the JSON format and ensure all required fields are present.
API endpoint errors: HTTP errors from the Fredhopper API (e.g., 400 Bad Request, 401 Unauthorized) indicate issues with request parameters or credentials. Review the error message returned by the API for guidance.
Network issues: Timeouts or connection errors suggest network problems; check firewall settings and internet connectivity.
To handle partial failures gracefully, enable the node's "Continue On Fail" option to process remaining items even if some fail.