myLIMS icon

myLIMS

Allows interaction with myLIMS API
Join our community

Actions13

Overview

This node integrates with the myLIMS system, allowing users to retrieve detailed information about accounts and works managed within myLIMS. Specifically, for the Account Infos operation, it fetches additional informational details related to a specific account by its ID.

Common scenarios include:

  • Retrieving extended metadata or supplementary info about an account in a laboratory information management system.
  • Automating workflows that require up-to-date account details for reporting or processing.
  • Integrating myLIMS account data into other systems or dashboards.

Example: Given an Account ID, the node will call the myLIMS API endpoint to get all associated "infos" for that account, returning structured JSON data representing those details.

Properties

Name Meaning
Account ID The unique numeric identifier of the account whose infos you want to retrieve. Example: 10

Output

The node outputs a JSON array where each item corresponds to the retrieved account info data from the myLIMS API. The structure depends on the API response but generally includes various informational fields related to the specified account.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the myLIMS API.
  • Needs an API authentication token or key configured in n8n credentials (referred generically as "an API key credential").
  • Network access to the myLIMS service endpoint.

Troubleshooting

  • API Request failed: This error indicates the node could not successfully communicate with the myLIMS API. Common causes include invalid or missing API credentials, network issues, or incorrect Account ID values.
    • Verify that the API key credential is correctly set up and has sufficient permissions.
    • Confirm the Account ID exists and is valid.
    • Check network connectivity to the myLIMS API endpoint.
  • Unsupported resource: If the resource or operation parameters are misconfigured, the node throws an unsupported resource error. Ensure the Resource is set to "Account" and Operation to "Account Infos" for this use case.

Links and References

Discussion