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 write custom scripts and pass variables dynamically. The node encodes the script in base64 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 automation pipelines.
- Dynamically modifying Taskt scripts with variables before execution.
Example: A user writes a Taskt script that automates filling out a form, then uses this node to run the script with different input values passed as variables.
Properties
| Name | Meaning |
|---|---|
| Script | The Taskt script code to be executed. |
| 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 from 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.
- Needs an API authentication token (referred generically as an API key credential) configured in the node credentials.
- Uses helper functions to replace variables in the script and encode the script in base64 before sending.
Troubleshooting
Common issues:
- Invalid or missing API authentication token will cause authentication failures.
- Malformed or incorrect Taskt script syntax may result in errors from the Taskt API.
- Incorrect variable names or missing variables can lead to unexpected script behavior.
Error messages:
- Errors thrown during the HTTP request to the Taskt API are caught and either cause the node to fail or return an error object if "Continue On Fail" is enabled.
- Typical error messages relate to network issues, authentication failures, or script execution errors reported by the Taskt API.
Resolution tips:
- Verify the API key and domain URL are correctly set in the credentials.
- Ensure the script syntax is valid and tested within the Taskt environment.
- Confirm all required variables are provided and correctly named.