Actions13
Overview
This node integrates with the myLIMS system, allowing users to retrieve detailed information about laboratory works and accounts via the myLIMS API. Specifically, for the "Work" resource and "Work" operation, it fetches data related to a specific work item identified by its Work ID. This is useful in scenarios where you need to automate retrieval of lab work details, such as fetching billing information or work status for further processing or reporting.
Practical examples include:
- Automatically retrieving billing details for a given work order to update financial systems.
- Fetching work metadata to trigger downstream workflows based on work status or attributes.
Properties
| Name | Meaning |
|---|---|
| Work ID | The unique numeric identifier of the work (billing) record to retrieve. Required to specify which work's information to fetch. |
Output
The node outputs JSON data representing the details of the specified work. The structure corresponds directly to the response from the myLIMS API endpoint /works/{workId}. It typically includes fields such as work identifiers, statuses, dates, associated samples, pricing, and other metadata relevant to the work.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the myLIMS API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The node uses HTTP GET requests to fetch data from the myLIMS REST endpoints.
Troubleshooting
Common issues:
- Invalid or missing Work ID will cause the API request to fail.
- Network connectivity problems or incorrect API credentials will result in authentication errors.
- Requesting a non-existent Work ID may return a 404 error from the API.
Error messages:
API Request failed: <message>indicates that the underlying HTTP request to myLIMS failed. Check the message for specifics such as authentication failure, invalid parameters, or server errors.
Resolutions:
- Ensure the Work ID is correctly provided and exists in the myLIMS system.
- Verify that the API key or authentication token is valid and has sufficient permissions.
- Confirm network access to the myLIMS API endpoint.
Links and References
- myLIMS API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes