Actions11
Overview
This node integrates with the CoreSense system to perform various operations on different resources. Specifically, for the Transfer resource with the Search operation, it allows users to query transfer records in CoreSense. This is useful when you want to retrieve transfer data filtered or ordered by specific criteria, such as a particular Transfer ID or sorted by certain fields.
Common scenarios include:
- Fetching details of a specific transfer by its ID.
- Retrieving a list of transfers ordered by their creation timestamp or document IDs.
- Exporting transfer data for reporting or further processing.
Example: You might use this node to search for all transfers related to a particular shipment or to get the latest transfers sorted by their timestamps.
Properties
| Name | Meaning |
|---|---|
| Transfer ID | (Optional) Specify a numeric ID of the transfer to search for. Can also be set via expression. |
| Order By | (Optional) Choose how to order the results. Options: ID, Master Receiving Document ID, Stamp (timestamp). |
| Return All | Whether to return all matching results or limit the number of returned items. |
| Limit | Maximum number of results to return if "Return All" is false. Minimum value is 1. |
Output
The node outputs JSON data representing the transfer records retrieved from CoreSense based on the search criteria. Each item in the output corresponds to a transfer record with its associated fields as provided by the CoreSense API.
If binary data were involved (not indicated here), it would typically represent files or attachments related to transfers, but this node focuses on JSON data output.
Dependencies
- Requires an active connection to CoreSense via an API key credential configured in n8n.
- The node depends on CoreSense's API availability and correct authentication.
- No additional external dependencies are indicated beyond the CoreSense API access.
Troubleshooting
- No results returned: Verify that the Transfer ID or other search parameters are correct and exist in CoreSense.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- Limit ignored or too many results: If "Return All" is false but more results are expected, check the "Limit" property to ensure it is set appropriately.
- Ordering issues: Confirm that the "Order By" field matches one of the allowed options; otherwise, the API may reject the request or default ordering may apply.
Links and References
- CoreSense API Documentation (generic link, replace with actual if available)
- n8n Expressions Guide - for using expressions in properties like Transfer ID