Launix API icon

Launix API

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

Actions8

Overview

The node provides integration with the Launix software API, enabling users to perform various data operations on Launix tables and custom actions. It supports creating, reading, updating, deleting records, listing items with filtering and sorting, uploading and downloading files, and executing custom API actions.

A common use case is automating workflows that interact with Launix databases, such as retrieving filtered lists of records, inserting new entries, or managing files stored in Launix. For example, a user might list all users from a specific table with certain filter criteria or download a file by its ID for further processing.

Properties

Name Meaning
Table The Launix table to operate on. Users select from searchable available tables.
Filter and Sort Parameters JSON object specifying GET parameters for filtering and sorting when listing items. Example keys: filter_user_ID, sort_user.

Output

  • The json output field contains the response data from the Launix API corresponding to the operation performed:
    • For List operation, it returns the retrieved list of items matching the filter and sort parameters.
    • For other operations (create, edit, delete, view, custom), it returns relevant result objects or status indicators.
  • When downloading files (retrieveFile operation), the node outputs binary data under the binary property with the file content and metadata such as filename and MIME type.
  • When uploading files (uploadFile operation), the node outputs a JSON confirmation including upload results.
  • Custom actions may return JSON data or binary PDF files depending on the action's response content type.

Dependencies

  • Requires an API key credential for authenticating requests to the Launix API.
  • Needs the base URL of the Launix instance configured in credentials.
  • Uses HTTP requests to communicate with Launix endpoints.
  • No additional external dependencies beyond standard n8n helpers and request utilities.

Troubleshooting

  • Missing Binary Property Error: When uploading files, if the specified binary property is not found on the input item, the node throws an error indicating the missing property. Ensure the binary data exists and the correct property name is set.
  • API Errors: If the Launix API returns an error, it will be thrown by the node. Check the API token validity, endpoint URLs, and permissions.
  • Invalid JSON in Filter Parameters: The filter and sort parameters must be valid JSON. Invalid JSON strings will cause parsing errors.
  • File Download Issues: If the file ID is incorrect or the file does not exist, the node may fail to retrieve the file. Verify the file ID and access rights.
  • Custom Action Parameter Mismatch: Providing incorrect or incomplete parameters for custom actions can lead to unexpected responses or errors. Use the node’s parameter mapping features to ensure correctness.

Links and References

Discussion