Actions11
Overview
This node integrates with the CoreSense platform to perform operations on various resources. Specifically, for the Order Item resource with the Search operation, it allows users to query order items based on optional filters such as Order Item ID and Order ID. Users can also control the sorting order of results and limit the number of returned entries.
Common scenarios include:
- Retrieving specific order items by their unique IDs.
- Fetching all order items related to a particular order.
- Sorting order items by different attributes like delivery timing or model ID.
- Paginating results by limiting the number of returned items.
Practical example: A user wants to find all order items associated with a given order number, sorted by delivery timing, and retrieve only the first 20 results.
Properties
| Name | Meaning |
|---|---|
| Order Item ID | (Optional) Filter by a specific order item ID. Can be set directly or via an expression. |
| Order ID (Num) | (Optional) Filter by a specific order ID number. Can be set directly or via an expression. |
| Order By | (Optional) Choose how to sort the search results. Options: Closed, Delivery Timing, ID, Model ID, Order Num |
| Return All | Whether to return all matching results or limit the output. |
| Limit | Maximum number of results to return when "Return All" is false. Minimum value is 1. |
Output
The node outputs JSON data representing the list of order items matching the search criteria. Each item in the output array corresponds to an order item object with its properties as defined by the CoreSense API.
If binary data were involved (not indicated here), it would typically represent files or attachments related to order items, but this node focuses on JSON data output.
Dependencies
- Requires an active connection to the CoreSense API using a valid API authentication token configured in n8n credentials.
- The node depends on internal routing and action modules to handle requests to CoreSense services.
- No additional external dependencies are required beyond the CoreSense API access.
Troubleshooting
- No results returned: Verify that the filter parameters (Order Item ID, Order ID) are correct and exist in CoreSense. Also, check if the "Return All" and "Limit" settings are appropriate.
- Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Invalid parameter values: Make sure numeric fields receive numbers and options are selected from the provided lists.
- API rate limits or connectivity issues: Check network connectivity and CoreSense API status.
Links and References
- CoreSense API Documentation (hypothetical link for reference)
- n8n Expressions Documentation - for using expressions in input fields.