Launix API icon

Launix API

Access your Launix software, retrieve data, insert items
Join our community

Actions8

Overview

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

Common scenarios include:

  • Updating records in a specific table (Edit operation).
  • Modifying dataset entries by specifying columns and values.
  • Automating workflows that require interaction with Launix data tables.
  • Performing custom API actions beyond standard CRUD operations.

For example, you can use this node to update user information in a "Users" table by specifying the dataset ID and the columns to change.

Properties

Name Meaning
Table The target table in Launix to work on. Selectable from a searchable list of available tables.
Dataset ID Identifier of the dataset entry you want to edit.
Columns Mapping of column names to new values for updating the dataset. Supports defining multiple columns.

Output

The node outputs JSON data representing the result of the edit operation:

  • For the Edit operation, the output JSON contains a result field with the response from the Launix API after updating the item.
  • If an error occurs, the node either throws an error or returns an error object paired with the input item if "Continue On Fail" is enabled.
  • No binary data is output for the Edit operation.

Example output JSON structure for a successful edit:

{
  "result": {
    /* API response fields indicating success or updated data */
  }
}

Dependencies

  • Requires an API key credential for authenticating with the Launix API.
  • Needs network access to the Launix base URL specified in the credentials.
  • Uses HTTP requests to interact with Launix endpoints such as /TablesAPI/{table}/{operation}.

Troubleshooting

  • Missing or invalid credentials: Ensure the API key credential is correctly configured and has access rights.
  • Invalid table or dataset ID: Verify that the selected table exists and the dataset ID corresponds to an existing record.
  • Incorrect column mappings: Make sure the columns property includes valid column names and appropriate values.
  • API errors: The node surfaces API errors; check the error message for details and verify API endpoint availability.
  • JSON parsing issues: When providing filter parameters or other JSON inputs, ensure valid JSON syntax.

If the node throws an error related to missing binary data, it usually pertains to file upload/download operations, not the Edit operation.

Links and References

Discussion