Actions11
Overview
The node integrates with the CoreSense platform to perform various operations on different resources. Specifically, for the Order resource with the Search operation, it allows users to query orders based on optional filters and sorting criteria. This is useful in scenarios where you want to retrieve order data programmatically, such as fetching recent orders, filtering by specific order IDs, or sorting orders by status or date.
Practical examples include:
- Retrieving all orders placed by a particular client.
- Searching for orders with a specific status or financial condition.
- Exporting order data sorted by cancellation date for reporting.
Properties
| Name | Meaning |
|---|---|
| Order ID | (Optional) Specify an exact order ID to search for. Can also use expressions to dynamically set it. |
| Order By | (Optional) Choose how to sort the search results. Options: Cancelled, Client ID, Google Financial Status, Google Fulfillment Status, Google Order Number, ID, Locked, Order Status, Originating Brand ID, Originating Channel ID, Payment Invoice Number, Salesman, Stamp. Default is "Cancelled". |
| Return All | Whether to return all matching results or limit the number of results returned. |
| Limit | Maximum number of results to return if "Return All" is false. Minimum value is 1, default is 50. |
Output
The node outputs JSON data representing the list of orders matching the search criteria. Each item in the output array corresponds to an order object containing its details as provided by the CoreSense API. The structure typically includes fields like order ID, client information, status, timestamps, and other relevant metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the CoreSense API via an API key credential configured in n8n.
- The node depends on internal routing logic and methods imported from bundled source files to handle the API requests.
- No additional external services are explicitly required beyond CoreSense.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Specifying an invalid Order ID or unsupported filter values may result in empty responses or errors.
- Exceeding rate limits imposed by CoreSense API could lead to throttling errors.
- Error messages:
- Authentication errors indicate problems with the API key setup; verify credentials in n8n.
- Validation errors suggest incorrect input parameters; check property values especially for "Order ID" and "Order By".
- Network or timeout errors require checking connectivity and CoreSense service status.
Links and References
- CoreSense API Documentation (hypothetical link)
- n8n Expressions Documentation – for using expressions in properties like Order ID