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 locale settings among other resources. Specifically, for the Locale resource and the Set Default Locale operation, it allows users to set a default locale for a given tenant and environment in the Fredhopper system.

This is useful in scenarios where you want to programmatically control the default language or regional setting used by your product discovery or catalog system, ensuring that content is served in the correct locale context.

Practical example:
You might use this node to update the default locale to "en" (English) for your staging environment before running tests or to switch the default locale dynamically based on user preferences or deployment pipelines.

Properties

Name Meaning
Tenant The tenant identifier within the Fredhopper system (e.g., "solutions").
Environment The environment name where the locale setting applies (e.g., "cidp-test").
FHR Validation Boolean flag indicating whether Fredhopper validation should be applied (true or false).
Default Locale The locale code to set as the default (e.g., "en", "fr", "de").

Output

The output of the node after setting the default locale is the raw response from the Fredhopper API call. This typically confirms the success of the operation but does not return detailed JSON data. The output is returned as a JSON array containing the response body or an empty string if no content is returned.

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 internally to obtain an access token before making API requests.
  • The following environment-specific parameters must be provided: tenant, environment, and optionally the FHR validation flag.
  • The node expects the Fredhopper API base URLs and authentication endpoints to be correctly configured in the 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 locale codes:
    Setting a default locale with an unsupported or invalid locale code may cause the API to reject the request. Ensure the locale code matches those supported by your Fredhopper instance.

  • Network or API errors:
    Errors related to connectivity or unexpected API responses will be surfaced. Check network connectivity and API endpoint availability.

  • Permission issues:
    Insufficient permissions for the API user can cause failures. Confirm that the API user has rights to modify locale settings.

  • Empty or malformed input:
    Providing empty strings or incorrect types for required properties (tenant, environment, default locale) will cause errors.

Links and References

Discussion