Actions34
- Banking Operation (India) Actions
- Catalog Operation Actions
- Contact Operation Actions
- HRMS Operation (India) Actions
- Purchase Operation (India) Actions
- Sales Operation (India) Actions
- Tax Operation (India) Actions
Overview
This node interacts with a catalog service via an API to retrieve catalog data. Specifically, the "Get All Catalogs" operation allows users to fetch multiple catalog entries either by searching for catalogs by name or by limiting the number of results per page.
Common scenarios where this node is beneficial include:
- Retrieving a list of product or service catalogs for display or further processing.
- Searching catalogs by a specific term to find matching entries.
- Paginating through catalogs by specifying how many items to retrieve per request.
Practical examples:
- An e-commerce workflow that needs to pull all available product catalogs to update inventory or pricing.
- A CRM integration that searches catalogs by name to link products to customer orders.
- Reporting workflows that aggregate catalog data with limits on the number of records fetched.
Properties
| Name | Meaning |
|---|---|
| Search Type | Choose how to search catalogs: "Search by Name" (search_term) or "Search by Limit" (limit) |
| Search Term | The text string to search catalog names for (only shown if Search Type is "Search by Name") |
| Limit (Per Page) | Number of catalog entries to return per page (shown for both search types) |
Output
The node outputs JSON data containing the retrieved catalog entries. Each item in the output corresponds to a catalog record returned by the API. The structure typically includes catalog details such as IDs, names, and other metadata as provided by the external catalog service.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential and user authentication credentials (email and password) to authenticate with the external catalog API.
- The node performs HTTP requests to the configured API URL endpoint.
- Proper configuration of these credentials and API URL in n8n is necessary for successful execution.
Troubleshooting
- Authentication Failures: If the node fails to login, it will throw an error indicating authentication failure. Verify that the API key, email, and password credentials are correct and have sufficient permissions.
- Empty or Unexpected Data: If the API returns no data or an unexpected structure, ensure the search parameters are valid and the API service is operational.
- Network Issues: Connectivity problems to the API endpoint can cause request failures. Check network access and API availability.
- Invalid Property Values: Providing invalid values for "Search Term" or "Limit" may result in errors or empty results. Validate input before execution.
Links and References
- No direct external links are present in the source code. For more information, consult the documentation of the external catalog API used by this node.