Actions20
- Catalog Actions
- Category Tree Actions
- Item Actions
- Locale Actions
Overview
This node interacts with the Fredhopper Product Discovery API, specifically supporting operations related to managing locales among other resources. The "Delete Default Locale" operation under the "Locale" resource allows users to delete the currently set default locale for a given tenant and environment.
Typical use cases include:
- Removing a default locale configuration when it is no longer needed or before setting a new default locale.
- Managing localization settings programmatically in an automated workflow.
- Cleaning up locale configurations as part of environment maintenance or deployment processes.
For example, if you have a tenant "solutions" running in the "cidp-test" environment and want to remove the default locale setting (e.g., "en"), this node operation will send the appropriate request to the Fredhopper API to delete that default locale.
Properties
| Name | Meaning |
|---|---|
| Tenant | The tenant identifier for which the locale is managed (e.g., "solutions"). |
| Environment | The environment context where the locale applies (e.g., "cidp-test"). |
| FHR Validation | Boolean flag indicating whether Fredhopper validation should be applied during the operation. |
| Default Locale | The locale code to delete as the default locale (e.g., "en"). Required for deleting or setting default locale. |
Output
The output JSON structure after executing the "Delete Default Locale" operation typically contains the response from the Fredhopper API confirming the deletion. It may look like:
{
"deleted": true
}
This indicates that the default locale was successfully deleted. If the operation fails, an error object or message will be returned instead.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Fredhopper Product Discovery API.
- The node uses Basic Authentication to obtain an access token, then uses Bearer token authentication for subsequent API requests.
- The following environment-specific parameters must be configured: tenant, environment, and optionally FHR validation flag.
- The node expects the Fredhopper API base URLs and credentials to be correctly set up in n8n credentials.
Troubleshooting
- Authentication errors: If the node throws an error about failing to obtain an access token, verify that the API credentials (username, password, auth URL) are correct and have sufficient permissions.
- Invalid tenant/environment: Ensure the tenant and environment values are valid and exist in the Fredhopper system.
- Locale not found: Attempting to delete a default locale that does not exist may result in an error or no-op; confirm the locale code is correct.
- Network issues: Connectivity problems to the Fredhopper API endpoint can cause timeouts or failures; check network access and firewall rules.
- API rate limits: Excessive requests might be throttled by the API; consider adding delays or retries if needed.