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 provide custom scripts and variables that get processed remotely. This node is beneficial in scenarios where you want to integrate Taskt automation workflows within n8n, enabling complex task automation triggered or enriched by n8n workflows.
For example, you might use this node to:
- Run a Taskt script that automates desktop tasks based on data processed earlier in an n8n workflow.
- Pass dynamic variables from n8n into a Taskt script to customize its behavior per execution.
- Integrate Taskt automation with other services orchestrated by n8n.
Properties
| Name | Meaning |
|---|---|
| Script | The Taskt script content as a string. This script will be sent to the Taskt API for execution. |
| Variables | A collection of key-value pairs representing variables to replace inside the script before sending it. Each variable has: - Variable: The name of the variable to replace. - Value: The value to substitute for the variable in the script. |
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 of the response depends on the Taskt API but typically includes execution results or error messages.
If the node encounters an error during execution and "Continue On Fail" is enabled, the output for that item will contain an error message describing the failure.
No binary data output is produced by this node.
Dependencies
- Requires access to a Taskt API endpoint, which must be configured via credentials providing:
- An authentication key (
AuthKey) for API authorization. - The domain URL of the Taskt API.
- An authentication key (
- Uses HTTP POST requests to send the script (base64 encoded) to the Taskt API.
- Relies on helper functions to replace variables in the script and encode the script in base64.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Malformed or empty scripts may result in errors from the Taskt API.
- Incorrect variable names or values might lead to unexpected script behavior.
- Network connectivity problems can prevent reaching the Taskt API.
Error messages:
- Errors thrown by the Taskt API are captured and returned in the output if "Continue On Fail" is enabled.
- If not enabled, errors will stop the node execution and display the error message.
Resolution tips:
- Verify that the API key and domain are correctly set in the credentials.
- Ensure the script syntax is valid and tested independently if possible.
- Double-check variable names match those expected in the script.
- Use "Continue On Fail" cautiously to handle partial failures gracefully.
Links and References
- Taskt Automation Platform – Official site for Taskt automation software.
- n8n Documentation – For general guidance on creating and using custom nodes and credentials.