Actions11
Overview
The node integrates with the CoreSense platform to perform various operations on different resources. Specifically, for the Product resource with the Search operation, it allows users to query products based on optional filters and ordering preferences. This is useful in scenarios where you want to retrieve product information dynamically within an automation workflow, such as fetching product details for inventory checks, syncing product data, or generating reports.
For example, you might use this node to:
- Search for a specific product by its ID.
- Retrieve a list of products ordered by their last modified date.
- Limit the number of returned products to avoid processing large datasets.
Properties
| Name | Meaning |
|---|---|
| Product ID | (Optional) Specify a product's unique identifier to search for a particular product. Can also be set using expressions. |
| Order By | (Optional) Choose how to order the search results. Options: ID, Last Modified Stamp, Manufacturer ID, Part Number, Type. |
| Return All | Whether to return all matching products or limit the number of results. |
| Limit | Maximum number of products to return when "Return All" is false. Minimum value is 1. |
Output
The node outputs JSON data representing the products retrieved from CoreSense based on the search criteria. The structure typically includes product attributes such as IDs, manufacturer details, part numbers, types, and timestamps. If binary data were involved (e.g., images), it would be included separately, but this node focuses on JSON product data only.
Dependencies
- Requires an API key credential for authenticating with the CoreSense service.
- The node depends on the CoreSense API being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an invalid Product ID or unsupported order option may result in empty responses or errors.
- Exceeding rate limits or network issues can cause request failures.
Error Messages:
- Authentication errors usually indicate incorrect or missing API keys; verify credentials.
- Validation errors may occur if input properties do not meet expected formats; ensure numeric fields like Product ID and Limit are valid numbers.
- Timeout or connectivity errors suggest network problems; check internet connection and CoreSense service status.
Links and References
- CoreSense API Documentation (hypothetical link)
- n8n Expressions Documentation – for using expressions in input fields