Overview
This node integrates with the Launix API to perform various data operations on tables within a Launix software environment. It supports creating, viewing, editing, deleting, listing items, uploading and retrieving files, and executing custom actions on datasets.
For the Delete operation specifically, the node deletes an item permanently from a specified table by its dataset ID. This is useful when you want to remove obsolete or incorrect records from your Launix-managed data tables programmatically.
Practical example:
You have a customer database managed in Launix, and you want to automate the removal of customers who have unsubscribed or whose accounts are closed. Using this node's Delete operation, you specify the table (e.g., "Customers") and the dataset ID of the customer record to delete it automatically as part of your workflow.
Properties
| Name | Meaning |
|---|---|
| Table | The target table in Launix where the deletion will occur. You select from a searchable list of available tables. |
| Dataset ID | The unique identifier of the dataset (record) you want to delete from the selected table. |
Output
- The output JSON contains a single field
deletedwhich holds the response from the Launix API after attempting the deletion. This typically confirms whether the deletion was successful. - No binary data is output for the Delete operation.
Example output JSON structure:
{
"deleted": {
// API response confirming deletion status
}
}
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 user must have appropriate permissions in Launix to delete records from the specified table.
Troubleshooting
Common issues:
- Invalid or missing dataset ID: Ensure the
Dataset IDproperty is correctly set and corresponds to an existing record. - Insufficient permissions: The API token used must have rights to delete records in the specified table.
- Incorrect table selection: Verify that the table name matches exactly one of the available tables in Launix.
- Invalid or missing dataset ID: Ensure the
Error messages:
- If the API returns an error, it will be thrown by the node. Common errors include authorization failures or "not found" errors if the dataset ID does not exist.
- To resolve, check credentials, verify dataset ID, and confirm table name correctness.
Links and References
- Launix API Documentation (hypothetical link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- General info on REST API Authentication