Launix Trigger
AI-generatedOverview
The Launix Trigger node starts an n8n workflow when data is created or edited in a specified Launix table. It is useful for automating processes that depend on changes in Launix database tables, such as syncing data, sending notifications, or updating other systems when new records are created.
Use Case Examples
- Trigger a workflow when a new record is created in a customer table to send a welcome email.
- Start a workflow when an order is created in the orders table to update inventory and notify the shipping department.
Properties
| Name | Meaning |
|---|---|
| Table | The Launix table to monitor for changes. The user selects the table from a searchable list of available tables. |
| Action | The type of action to trigger the workflow on. Currently, only the 'Created' action is supported, meaning the workflow triggers when new data is created in the selected table. |
Output
JSON
id- The ID of the created or edited record that triggered the workflow.
Dependencies
- Requires Launix API credentials for authentication and access to the Launix API endpoints.
Troubleshooting
- Ensure valid Launix API credentials are provided; missing or invalid credentials will cause errors.
- If the node fails to create or delete webhook triggers, verify the Launix API base URL and network connectivity.
- Common errors include 'No credentials returned!' if credentials are missing, and 'No trigger ID returned from Launix API' if the webhook registration fails.
- Check that the selected table exists and is accessible via the Launix API.
Links
- Launix API Documentation - Official documentation for the Launix API used by the node to manage webhook triggers and retrieve table information.