Actions20
- Catalog Actions
- Category Tree Actions
- Item Actions
- Locale Actions
Overview
This node interacts with the Fredhopper Product Discovery API, specifically managing catalogs among other resources. The Delete Catalog operation allows users to delete a specific catalog version from a given tenant and environment.
Typical use cases include:
- Removing outdated or incorrect catalog versions from your product discovery system.
- Automating catalog lifecycle management within CI/CD pipelines.
- Cleaning up test or temporary catalogs in different environments.
For example, if you have a catalog version that is no longer needed or was created by mistake, this node can be used to delete it programmatically by specifying the tenant, environment, and catalog version.
Properties
| Name | Meaning |
|---|---|
| Tenant | The tenant identifier under which the catalog exists. Example: "solutions". |
| Environment | The environment where the catalog is deployed. Example: "cidp-test". |
| Catalog Version | The specific version of the catalog to delete. This must be provided explicitly. |
Output
The output JSON for the Delete Catalog operation is a simple confirmation object indicating success:
{
"deleted": true
}
This confirms that the specified catalog version has been successfully deleted.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential (username, password, and auth URL) to authenticate against the Fredhopper Product Discovery API.
- The node uses OAuth2 client credentials flow to obtain an access token before making API requests.
- Network connectivity to the Fredhopper API endpoints (
https://items.attraqt.io/catalogs/...) is required. - Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
- Authentication failed: If the node cannot obtain an access token, check that the API credentials (username, password, auth URL) are correct and valid.
- Catalog not found or invalid version: Ensure the
Catalog Versionproperty matches an existing catalog version in the specified tenant and environment. - Network errors: Verify network connectivity and that the Fredhopper API endpoint is reachable.
- Permission issues: The API user must have sufficient permissions to delete catalogs.
- Unexpected errors: Enable "Continue On Fail" in the node settings to handle errors gracefully and inspect error messages returned in the output.
Links and References
- Fredhopper Product Discovery API Documentation (generic link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- OAuth2 Client Credentials Flow