Launix API icon

Launix API

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

Actions8

Overview

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

The Create operation specifically allows inserting new items into a selected Launix table by specifying values for its columns.

Common scenarios:

  • Automating data entry into Launix tables from other systems.
  • Bulk inserting records based on external triggers or workflows.
  • Integrating Launix with other applications where new data needs to be programmatically added.

Example:
You have a CRM system that collects leads, and you want to automatically insert these leads into a Launix "Contacts" table whenever a new lead is created.

Properties

Name Meaning
Table The Launix table where the new item will be inserted. You select this from a searchable list of available tables.
Columns The column values to set for the new item. You define mappings for each column in the selected table. All required columns must be provided.

Output

  • The output JSON contains an id field representing the identifier of the newly created item in the Launix table.
  • No binary data is produced by the Create operation.

Example output JSON:

{
  "id": "12345"
}

Dependencies

  • Requires an API key credential for authenticating with the Launix API.
  • The node makes HTTP requests to the Launix base URL configured in the credentials.
  • The Launix API must expose endpoints for tables and support POST requests to create new items.

Troubleshooting

  • Missing or invalid API credentials: Ensure the API key and base URL are correctly configured in the node credentials.
  • Table not found or inaccessible: Verify the selected table exists and the API user has permission to write to it.
  • Required columns missing: When mapping columns, all required fields must be provided; otherwise, the API may reject the request.
  • API errors: If the API returns an error, the node throws it unless "Continue On Fail" is enabled, in which case the error is included in the output for that item.
  • Invalid input data format: Make sure the column values match expected types (usually strings) as the node sends them as strings.

Links and References

Discussion