Launix API icon

Launix API

Access your Launix software, retrieve data, insert items

Overview

This node integrates with the Launix API, allowing users to perform various data operations on Launix software tables and datasets. It supports retrieving, creating, editing, deleting, listing items, uploading and downloading files, and executing custom actions defined in Launix.

For the View operation specifically, the node retrieves a single dataset item from a specified table by its dataset ID. This is useful when you want to fetch detailed information about a particular record stored in Launix.

Practical examples:

  • Fetching customer details from a "Customers" table by specifying the dataset ID.
  • Retrieving a specific invoice or order record for further processing or display.
  • Accessing configuration or metadata entries stored in Launix tables.

Properties

Name Meaning
Table The Launix table to work on. You select from a searchable list of available tables.
Dataset ID The identifier of the dataset (record) you want to view within the selected table.

Output

The output JSON contains the retrieved dataset item under the json property. The structure corresponds directly to the data returned by the Launix API for the requested dataset ID.

Example output JSON structure:

{
  "data": {
    /* dataset fields and values as returned by Launix */
  }
}

No binary data is produced for the View operation.

Dependencies

  • Requires an API key credential for authenticating with the Launix API.
  • Needs the base URL of the Launix instance configured in the credentials.
  • Uses HTTP requests to interact with Launix REST endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing dataset ID will cause the API to return an error or empty result.
    • Incorrect table selection may lead to "not found" errors if the dataset ID does not exist in that table.
    • Network or authentication failures can prevent successful API calls.
  • Error messages:

    • Errors returned by the Launix API are thrown and include the error message from the response.
    • If the node fails due to missing binary data (in other operations), it throws a clear error indicating which binary property is missing.
    • To handle errors gracefully, enable "Continue On Fail" in the node settings.

Links and References

Discussion