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 category trees, among other resources. Specifically, the "Delete a Category Tree" operation allows users to remove a specified version of a category tree from their environment and tenant in the Fredhopper system.

Common scenarios for this node include:

  • Cleaning up outdated or deprecated category trees.
  • Automating catalog maintenance workflows by removing unused category structures.
  • Integrating category tree management into broader product data pipelines.

For example, a user might automate the deletion of a category tree version after migrating to a new structure, ensuring that only relevant category trees remain active.

Properties

Name Meaning
Tenant The tenant identifier within which the category tree exists (e.g., "solutions").
Environment The environment name where the category tree is managed (e.g., "cidp-test").
Category Tree Name The exact name of the category tree to delete.
Category Tree Version The specific version of the category tree to delete.

Output

The output JSON object for the "Delete a Category Tree" operation contains a single field:

  • deleted: A boolean value set to true indicating that the category tree was successfully deleted.

Example output:

[
  {
    "deleted": true
  }
]

No binary data 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.
  • The API base URL is fixed to https://items.attraqt.io/.
  • Proper configuration of tenant and environment parameters is necessary to target the correct resource.

Troubleshooting

  • Authentication failures: If the node cannot obtain an access token, it will throw an error indicating authentication failure. Ensure that the API credentials (username, password, auth URL) are correctly configured and valid.
  • Resource not found: If the specified category tree name or version does not exist, the API may return an error. Verify that the category tree name and version are correct.
  • Permission issues: Insufficient permissions on the API key or tenant environment can cause request failures. Confirm that the API key has rights to delete category trees.
  • Network errors: Connectivity problems to the API endpoint will result in request errors. Check network access and proxy settings if applicable.

Links and References

Discussion