Launix Trigger icon

Launix Trigger

Starts the workflow when data is created/edited in Launix
Join our community

Overview

This node acts as a trigger for workflows based on events occurring in Launix, specifically when new data is created or edited in a selected table. It listens for changes in a specified Launix table and starts the workflow whenever a "created" action happens on that table.

Common scenarios where this node is useful include:

  • Automating processes immediately after new records are added to a Launix database table.
  • Synchronizing data between Launix and other systems by triggering workflows on data creation.
  • Sending notifications or performing validations when new entries appear in Launix tables.

For example, if you have a customer orders table in Launix, you can use this trigger to start a workflow every time a new order is created, enabling automated order processing or alerting.

Properties

Name Meaning
Table The specific Launix table to monitor for changes. You select from a searchable list of available tables.
Action The event type to trigger on. Currently, only the "Created" action (trigger when new data is created) is supported.

Output

The node outputs JSON data containing the id of the record that triggered the workflow. The output structure is:

{
  "id": "<record_id>"
}

This ID corresponds to the newly created record in the selected Launix table.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Launix API.
  • Needs access to the Launix instance base URL and token via credentials.
  • The node uses Launix REST API endpoints to manage webhook triggers and listen for events.
  • n8n must be able to receive incoming HTTP requests at the configured webhook URL.

Troubleshooting

  • No credentials returned!
    This error occurs if the node cannot retrieve the required API authentication credentials. Ensure that valid Launix API credentials are configured in n8n.

  • No trigger ID returned from Launix API
    Indicates failure to register the webhook trigger with Launix. Verify that the API token has sufficient permissions and that the base URL is correct.

  • Error checking trigger existence in Launix API
    Happens if the node cannot verify whether the webhook trigger still exists. Check network connectivity and API token validity.

  • If the workflow does not start on new data creation, confirm that the webhook URL is accessible from Launix and that the selected table and action are correct.

Links and References

Discussion