Actions11
Overview
The node integrates with the CoreSense platform to perform various operations on different resources. Specifically, for the Shipment resource and the Search operation, it allows users to query shipments based on optional criteria such as shipment ID, ordering preferences, and result limits. This is useful in scenarios where you want to retrieve shipment data programmatically, for example, to monitor shipping statuses, track specific shipments, or generate reports.
Practical examples include:
- Searching for a shipment by its unique ID.
- Retrieving a list of shipments ordered by their status or export state.
- Fetching all shipments or limiting the number of results returned for performance reasons.
Properties
| Name | Meaning |
|---|---|
| Shipment ID | (Optional) Specify a shipment's unique numeric ID to search for a particular shipment. Can also use expressions to dynamically set this value. |
| Order By | (Optional) Choose how to order the search results. Options: Associated Entity, Exported, ID, Status. |
| Return All | Whether to return all matching shipments or limit the number of results. |
| Limit | Maximum number of shipment records to return when "Return All" is false. Minimum value is 1. |
Output
The node outputs JSON data representing the shipment records that match the search criteria. Each item in the output contains shipment details as provided by the CoreSense API. The structure typically includes fields like shipment ID, status, associated entities, and export information.
There is no indication that the node outputs binary data 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 (
router) and action modules specific to each resource, including shipments. - No additional external dependencies are indicated beyond the CoreSense API access.
Troubleshooting
Common issues:
- Invalid or missing API credentials will prevent successful communication with CoreSense.
- Providing an invalid shipment ID or unsupported values for ordering may result in empty results or errors.
- Exceeding rate limits or network connectivity problems can cause request failures.
Error messages:
- Authentication errors typically indicate misconfigured or expired API keys; verify and update credentials.
- Validation errors may occur if input properties do not meet expected formats (e.g., non-numeric shipment ID).
- Timeout or network errors suggest connectivity issues; retry or check network settings.
Links and References
- CoreSense API Documentation (hypothetical link)
- n8n Expressions Documentation – for using expressions in input fields
- n8n Node Development Guide