Actions20
- Catalog Actions
- Category Tree Actions
- Item Actions
- Locale Actions
Overview
This node interacts with the Fredhopper Product Discovery API, specifically supporting multiple resources including Locale. For the Locale resource, it supports operations such as getting, setting, and deleting the default locale for a given tenant and environment.
The Get Default Locale operation retrieves the currently set default locale for a specified tenant and environment. This is useful in scenarios where you need to programmatically confirm or use the default language/locale settings configured in your Fredhopper environment, for example, to ensure that product data or catalog information is displayed in the correct locale.
Practical examples:
- Automatically fetching the default locale before syncing product data to ensure consistency.
- Validating locale settings during deployment or integration workflows.
- Using the default locale value to customize user experiences or reports.
Properties
| Name | Meaning |
|---|---|
| Tenant | The tenant identifier (e.g., "solutions") specifying which tenant's locale to access. |
| Environment | The environment name (e.g., "cidp-test") indicating the target environment for the request. |
| FHR Validation | Boolean flag to enable or disable Fredhopper validation on the request (true or false). |
Output
The output JSON contains the response from the Fredhopper API for the default locale retrieval. It typically includes details about the current default locale configuration for the specified tenant and environment.
Example structure (simplified):
{
"defaultLocale": "en",
"tenant": "solutions",
"environment": "cidp-test",
"fhrValidation": false
}
If the API returns additional metadata or status fields, those will also be included in the output JSON.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Fredhopper Product Discovery API.
- The node uses Basic Authentication to obtain an OAuth2 bearer token, then uses this token for subsequent API requests.
- The API base URL used is
https://items.attraqt.io. - Proper configuration of credentials with username, password, and auth URL is necessary.
- Network connectivity to the Fredhopper API endpoints is required.
Troubleshooting
Authentication failed: Failed to obtain access token
This error indicates issues with the provided credentials or authentication endpoint. Verify that the API key credential is correctly configured with valid username, password, and auth URL.The operation "getDefaultLocale" is not supported!
This error occurs if an unsupported operation is selected. Ensure the operation matches exactly one of the supported options for the Locale resource.Network or HTTP errors
Check network connectivity and API endpoint availability. Also verify that tenant and environment parameters are correct and exist in the Fredhopper system.Invalid or missing parameters
Make sure all required properties (Tenant, Environment, FHR Validation) are provided and valid.If the node is set to continue on fail, errors will be returned as part of the output JSON with an
errorfield instead of stopping execution.
Links and References
- Fredhopper Product Discovery API Documentation (example placeholder, replace with actual URL if available)
- n8n Documentation - Creating Custom Nodes
- OAuth2 Authentication Concepts: https://oauth.net/2/
This summary focuses on the Locale resource and the Get Default Locale operation as requested.