Custom Action
AI-generatedOverview
This node allows users to perform custom actions on a specified table within the Launix API. It is useful for executing specific API-defined actions that are not covered by standard CRUD operations. For example, sending an invoice or triggering a custom workflow defined in the Launix system. Users select the target table, choose a custom action, and provide any required parameters for that action.
Use Case Examples
- Triggering a custom invoice send action on the 'Invoices' table with specific parameters.
- Executing a custom report generation action on a 'Reports' table with user-defined parameters.
Properties
| Name | Meaning |
|---|---|
| Table | The table on which the custom action will be performed. This is a required field and must be selected from a searchable list of tables. |
| Action | The specific custom action to execute on the selected table. This is required and can be chosen from a searchable list of available custom actions or specified by an expression. |
| Action Parameters | Parameters required by the custom action as defined by the API descriptor. Users provide values for these parameters to customize the action execution. |
| Dataset ID | The identifier of the dataset on which the custom action is to be performed. This is required for operations that target a specific dataset. |
Output
JSON
json- The JSON response from the Launix API after executing the custom action. This may include the result of the action, status information, or any returned data.binary- If the custom action returns a PDF file (e.g., a generated report), it is provided as binary data with metadata such as file name and content type.
Dependencies
- Launix API
- An API key credential for authentication with the Launix API
Troubleshooting
- Missing or incorrect table selection will cause the node to throw an error indicating the table was not found.
- If the custom action is not specified or invalid, the node will throw an error.
- Incorrect or missing action parameters may cause the API call to fail or return an error.
- If the API returns a PDF file, the node handles it as binary data; failure to handle this correctly may cause issues.
- Network or authentication errors will result in API request failures; ensure the API key credential is valid and the base URL is correct.
Links
- n8n Expressions - Documentation on how to use expressions in n8n, useful for specifying dynamic values such as the custom action ID.