Overview
This node, named "Taskt SL," is designed to perform operations related to Taskt by executing a user-provided script along with optional variables. It allows users to input a script as a string and define multiple key-value pairs as variables that can be used within the script execution context.
Common scenarios where this node would be beneficial include:
- Automating custom workflows that require running scripts with dynamic parameters.
- Integrating Taskt automation tasks into n8n workflows by passing scripts and variables dynamically.
- Testing or prototyping Taskt scripts with different sets of variables without changing the script itself.
For example, a user might provide a script that performs a specific Taskt operation and pass variables such as credentials or configuration options through the "Variables" property to customize the behavior at runtime.
Properties
| Name | Meaning |
|---|---|
| Script | The script content to execute, provided as a string. |
| Variables | A collection of key-value pairs where each "Variable" is the name of the variable key, and "Value" is the value assigned to that key. Multiple variables can be added. |
Output
The output of the node is an array of JSON objects. Each item in the output corresponds to an input item processed by the node. The structure of each output JSON object is currently minimal and static, containing a single key "test" with the value "test".
Example output JSON for each item:
{
"test": "test"
}
No binary data output is produced by this node.
Dependencies
- Requires an API authentication credential for Taskt (referred generically as an API key credential).
- No other external dependencies are explicitly required based on the source code.
- The node uses standard n8n workflow utilities for error handling and input/output management.
Troubleshooting
- Empty or invalid script: If the "Script" property is empty or contains invalid code, the node does not currently process it meaningfully; users should ensure valid script content is provided.
- Error handling: If an error occurs during processing, and the node is configured to continue on failure, the error message will be included in the output JSON under an
errorkey. Otherwise, the node will throw an error and stop execution. - No meaningful output: Currently, the node returns a static test object regardless of input. Users expecting dynamic script execution results may need to extend or modify the node's implementation.
Links and References
- n8n Documentation – For general guidance on creating and using custom nodes.
- Taskt official website or documentation (not linked here due to lack of explicit URL in source).