Actions13
Overview
This node integrates with the myLIMS system API to retrieve data related to laboratory work management. Specifically, for the Work Sample Price Items operation, it fetches pricing details associated with a particular sample within a work order. This is useful in scenarios where you need to programmatically access or analyze cost components of lab samples, such as generating reports, automating billing processes, or integrating pricing data into other systems.
For example, a lab manager could use this node to automatically pull price items for a given sample ID to verify costs before invoicing or to track pricing trends over time.
Properties
| Name | Meaning |
|---|---|
| Sample ID | The unique identifier of the sample for which price items are requested (required). |
| Top | Maximum number of price item records to return (default is 50). |
| Filter | Optional filter string to refine the query results, following the API's filtering syntax. |
Output
The node outputs an array of JSON objects representing the price items associated with the specified sample. Each object corresponds to a price item record retrieved from the myLIMS API. The exact structure depends on the API response but typically includes fields such as price item identifiers, descriptions, amounts, and related metadata.
No binary data output is produced by this operation.
Dependencies
- Requires connection to the myLIMS API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node uses HTTP GET requests to specific endpoints based on the resource and operation parameters.
Troubleshooting
Common issues:
- Missing or invalid Sample ID will cause the request to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Improperly formatted filter strings may cause the API to reject the query.
- Requesting too many records without pagination might lead to performance issues or API limits.
Error messages:
API Request failed: ...indicates that the underlying HTTP request to the myLIMS API did not succeed. Check network connectivity, API endpoint availability, and credential validity.Unsupported resource: workor similar means the resource or operation name was not recognized; ensure correct property values are set.
Links and References
- myLIMS API documentation (refer to your organization's internal or public API docs for detailed endpoint and filter syntax)
- n8n documentation on creating and using credentials and HTTP request nodes for API integrations