Actions20
- Catalog Actions
- Category Tree Actions
- Item Actions
- Locale Actions
Overview
The node integrates with the Fredhopper Product Discovery API to manage product items and related resources. Specifically, the Patch Items operation allows users to update existing product items partially by sending patch data to the API. This is useful when you want to modify certain attributes of multiple items without replacing the entire item data.
Common scenarios include:
- Updating prices or availability for a batch of products.
- Modifying specific fields like descriptions or tags on existing items.
- Applying partial updates efficiently without full data replacement.
Example: You have a catalog of products and want to update only the stock levels for several items based on recent inventory changes. Using this node's Patch Items operation, you can send just the stock level changes in JSON format, and the API will apply those patches accordingly.
Properties
| Name | Meaning |
|---|---|
| Tenant | The tenant identifier (e.g., "solutions") specifying the customer or client environment. |
| Environment | The environment name (e.g., "cidp-test") indicating the deployment stage or instance. |
| FHR Validation | Boolean flag to enable or disable Fredhopper validation during the request. |
| Product Data | JSON string containing the patch data for the items to be updated. |
Output
The output is a JSON object representing the response from the Fredhopper Product Discovery API after applying the patch operation. It typically contains information about the success or failure of the patch request, including any updated item details or error 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 performs OAuth2 client credentials flow internally to obtain a bearer token before making requests.
- Network access to
https://items.attraqt.ioendpoints is required. - No additional external dependencies beyond standard HTTP requests.
Troubleshooting
- Authentication failures: If the node cannot obtain an access token, check that the provided API credentials (username, password, auth URL) are correct and valid.
- Invalid JSON in Product Data: Ensure the patch data JSON string is well-formed and matches the expected schema for patching items.
- API errors: The API may return errors if the tenant/environment parameters are incorrect or if the patch data references non-existent items.
- Network issues: Verify connectivity to the Fredhopper API endpoint.
- Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error details in the output.
Links and References
- Fredhopper Product Discovery API Documentation
- OAuth 2.0 Client Credentials Flow
- n8n HTTP Request Node Documentation (for understanding underlying request mechanics)