Fredhopper Product Discovery icon

Fredhopper Product Discovery

Interact with Fredhopper Product Discovery API

Actions20

Overview

This node integrates with the Fredhopper Product Discovery API to manage item schemas within a specified tenant and environment. Specifically, the "Create an Item Schema" operation allows users to create new item schemas by sending schema data to the API.

Common scenarios where this node is beneficial include:

  • Automating the creation of product data schemas in e-commerce platforms.
  • Managing structured product information for search and discovery systems.
  • Integrating schema management into CI/CD pipelines for catalog updates.

For example, a user can define a JSON schema representing product attributes and use this node to create that schema in the Fredhopper system automatically, ensuring consistent data structure across environments.

Properties

Name Meaning
Tenant The tenant identifier under which the item schema will be created (e.g., "solutions").
Environment The environment context for the schema (e.g., "cidp-test").
Schema Tenant The tenant for the schema operation; typically same as Tenant but explicitly settable.
Schema Environment The environment for the schema operation; typically same as Environment but explicit.
Schema Data The JSON string containing the schema definition to be created.

Output

The output is a JSON object representing the response from the Fredhopper API after creating the item schema. This typically includes details about the newly created schema such as its name, version, and other metadata returned by the API.

Example output structure (simplified):

{
  "name": "exampleSchema",
  "version": "1.0",
  "description": "Schema description",
  "created": "2024-01-01T00:00:00Z",
  "otherMetadata": { ... }
}

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 uses OAuth2 client credentials flow to obtain an access token before making API requests.
  • Network connectivity to the Fredhopper API endpoints (https://items.attraqt.io/item-schemas) is required.
  • No additional external libraries beyond n8n's built-in HTTP request helpers are used.

Troubleshooting

  • Authentication failures: If the node cannot obtain an access token, ensure that the provided API credentials (username, password, auth URL) are correct and have sufficient permissions.
  • Invalid schema data: The schemaData property must be a valid JSON string representing the schema. Malformed JSON or invalid schema definitions will cause API errors.
  • API endpoint errors: Errors from the Fredhopper API (e.g., 400 Bad Request, 401 Unauthorized) will be surfaced. Check the error message for details and verify tenant/environment values.
  • Network issues: Ensure that the n8n instance has network access to the Fredhopper API endpoints.

Links and References

Discussion