Overview
This node allows users to execute Taskt scripts by sending them to a Taskt API endpoint. It is designed for automating tasks using the Taskt automation platform, where users can define custom scripts and pass variables dynamically. The node encodes the script and sends it along with authentication headers to the Taskt service, then returns the response.
Common scenarios include:
- Automating repetitive desktop or web tasks by running Taskt scripts remotely.
- Integrating Taskt automation workflows into larger n8n workflows.
- Dynamically modifying Taskt scripts with variables before execution.
Example: A user can write a Taskt script that interacts with a web application, pass dynamic values as variables from previous workflow steps, and execute the script via this node to automate data entry.
Properties
| Name | Meaning |
|---|---|
| Script | The Taskt script code to be executed. This is a string containing the automation commands. |
| Variables | A collection of key-value pairs representing variables to replace in the script before execution. Each variable has: - Variable: The name of the variable in the script (e.g., v_Message). - Value: The value to substitute for the variable. |
Output
The node outputs an array of JSON objects, each containing a response field. This field holds the raw response returned by the Taskt API after executing the script. The structure depends on the API's response but typically includes execution results or error messages.
No binary data output is produced by this node.
Dependencies
- Requires access to a Taskt API endpoint, which must be configured with:
- An API domain URL.
- An authentication key credential for authorization.
- The node uses an external helper function (
replaceVariablesInScript) to substitute variables in the script before encoding and sending. - Network connectivity to the Taskt API service is necessary.
Troubleshooting
- Authentication errors: If the API key or domain is incorrect or missing, requests will fail. Verify credentials are correctly set up.
- Script errors: Malformed or invalid Taskt scripts may cause the API to return errors. Validate script syntax before execution.
- Variable substitution issues: Ensure variables used in the script match those defined in the "Variables" property; otherwise, replacements may not occur as expected.
- Network errors: Connectivity problems to the Taskt API domain will cause request failures.
- Error handling: If the node is set to continue on failure, errors are returned in the output JSON under an
errorfield; otherwise, the node execution stops with an error message.
Links and References
- Taskt Automation Platform – Official site for Taskt automation software.
- n8n Documentation on Creating Custom Nodes – For understanding node development concepts.