Overview
This node allows users to execute Taskt scripts by sending them to a Taskt API endpoint. It supports two input methods for providing variables that can be injected into the script before execution: either as individual variables ("One By One") or as a JSON block ("Json Block"). The node replaces placeholders in the script with these variables, encodes the script, and sends it via an HTTP POST request to the configured Taskt API.
Common scenarios include automating tasks that require running custom Taskt scripts with dynamic data inputs, such as automating desktop workflows, processing data, or integrating Taskt automation within an n8n workflow.
Example use case:
- A user wants to run a Taskt script that performs file operations on their machine, passing different filenames or parameters dynamically from previous nodes in the workflow.
Properties
| Name | Meaning |
|---|---|
| Input Method | Method to provide variables for the script. Options: "Json Block" (all variables as JSON) or "One By One" (individual variables). |
| Script | The Taskt script content as a string, which may contain placeholders for variables to be replaced before execution. |
| Variables | (Shown only if Input Method is "One By One") A collection of variable-value pairs to replace in the script. Each variable has a name and a corresponding value. |
| Variables (JSON) | (Shown only if Input Method is "Json Block") A JSON string representing all variables to replace in the script. |
Output
The node outputs an array of items where each item contains a json object with a single property:
response: The response returned from the Taskt API after executing the script. This typically includes any output or result from the Taskt script execution.
No binary data output is produced by this node.
Dependencies
- Requires access to a Taskt API endpoint, which must be configured with an API key credential.
- The node expects credentials containing at least an authentication key (
authKey) and the API domain URL (domain). - Uses helper functions from bundled dependencies to replace variables in the script and encode the script in base64 before sending.
Troubleshooting
Error: Invalid JSON in Variables (JSON)
If using the "Json Block" input method, ensure the JSON string is valid and properly formatted. Parsing errors will cause the node to fail.Error: API Request Failed
If the Taskt API endpoint is unreachable or returns an error, the node will throw an error unless "Continue On Fail" is enabled. Verify the API domain URL and authentication key are correct.Variable Replacement Issues
If variables are not replaced correctly in the script, check that variable names match exactly between the script placeholders and the provided variables.Empty or Missing Script
Ensure the "Script" property is not empty; otherwise, the node will send an empty script to the API, likely resulting in an error.
Links and References
- Taskt Automation – Official site for Taskt automation software.
- n8n Documentation on Creating Custom Nodes – For understanding how to build and configure nodes like this one.