Overview
This node, named "Taskt SL," is designed to perform operations involving the execution of a user-provided script with variable substitution. It allows users to input a script as a string and define multiple variables that can be dynamically replaced within that script during execution. This functionality is useful in scenarios where dynamic scripting or templating is needed, such as generating customized commands, automating repetitive tasks with variable inputs, or preparing scripts for external systems.
For example, a user might provide a script template containing placeholders and supply corresponding variable values to generate a fully resolved script for further processing or execution.
Properties
| Name | Meaning |
|---|---|
| Script | The script text to execute or process. It can contain placeholders for variables. |
| Variables | A collection of key-value pairs where each key is a variable name and the value is its replacement text in the script. Multiple variables can be added. |
Output
The node outputs an array of JSON objects, each representing the result of processing the script with the provided variables for each input item. The output JSON structure corresponds to the transformed script or the result of the variable replacement operation.
If an error occurs during script processing for an item and the node is configured to continue on failure, the output for that item will include an error field describing the issue.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential (referred generically) to interact with the underlying service or library responsible for variable replacement in scripts.
- Uses an external helper function (
replaceVariablesInScript) from a bundled dependency to perform the variable substitution logic.
Troubleshooting
Common issues:
- Errors in the script syntax or invalid variable references may cause the node to throw errors.
- Missing or incorrectly defined variables can lead to incomplete or failed substitutions.
- If the node is not configured to continue on failure, any error during script processing will stop the workflow execution.
Error messages:
- Errors thrown during variable replacement will include descriptive messages indicating the problem (e.g., undefined variable, syntax error).
- To resolve, verify the script syntax and ensure all referenced variables are properly defined in the Variables property.
Links and References
- No external links are provided in the source code. For more information on scripting and variable substitution, consult relevant documentation or resources related to the scripting language or templating engine used.