Fredhopper Product Discovery icon

Fredhopper Product Discovery

Interact with Fredhopper Product Discovery API

Actions20

Overview

This node interacts with the Fredhopper Product Discovery API to manage item schemas within a specified tenant and environment. Specifically, the "Delete an Item Schema" operation allows users to delete a particular version of an item schema by specifying its name and version.

Common scenarios for this node include:

  • Removing outdated or deprecated item schemas from a product catalog.
  • Cleaning up test or temporary schemas in development or staging environments.
  • Automating schema lifecycle management as part of a CI/CD pipeline for product data.

Practical example:

  • A user wants to delete version "1.0" of the "electronics" item schema in the "solutions" tenant on the "cidp-test" environment to ensure only the latest schema versions are active.

Properties

Name Meaning
Tenant The tenant identifier where the item schema exists (e.g., "solutions").
Environment The environment context for the tenant (e.g., "cidp-test").
FHR Validation Boolean flag indicating whether Fredhopper validation is enabled (not used in this op).
Schema Tenant Tenant under which the item schema is managed (usually same as Tenant).
Schema Environment Environment under which the item schema is managed (usually same as Environment).
Schema Name The name of the item schema to delete (required).
Schema Version The specific version of the item schema to delete (required).

Output

The output JSON contains a simple confirmation object indicating successful deletion:

{
  "deleted": true
}

This confirms that the specified item schema version was deleted successfully.

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.
  • The API endpoint for deleting item schemas is https://items.attraqt.io/item-schemas/{schemaName}/{schemaVersion} with query parameters for tenant and environment.
  • Proper network connectivity to the Fredhopper API service is required.

Troubleshooting

  • Authentication failed: If the node cannot obtain an access token, check that the API credentials (username, password, auth URL) are correct and have sufficient permissions.
  • Schema not found: If the specified schema name or version does not exist, the API may return an error. Verify the exact schema name and version.
  • Permission denied: Ensure the API credentials have rights to delete item schemas in the specified tenant and environment.
  • Network errors: Confirm that the Fredhopper API endpoint is reachable from the n8n instance.
  • Invalid parameters: Make sure all required properties (schemaName, schemaVersion, schemaTenant, schemaEnvironment) are provided and correctly formatted.

Links and References

Discussion