Taskt SL icon

Taskt SL

Perform Taskt operations
Join our community

Overview

This node allows users to perform operations with Taskt, a robotic process automation (RPA) tool. It sends a base64-encoded script along with optional variables to the Taskt API for execution. This is useful for automating repetitive tasks or workflows that require interaction with external systems via Taskt scripts.

Typical use cases include:

  • Automating desktop or web tasks by sending custom Taskt scripts.
  • Dynamically injecting variables into Taskt scripts before execution.
  • Integrating Taskt-based automation within larger n8n workflows.

Properties

Name Meaning
Script The Taskt script content encoded in base64 format to be executed by the Taskt API.
Variables A collection of key-value pairs representing variables to inject into the script before sending it. Each variable has:
- Variable: The name/key of the variable.
- Value: The value to assign to that variable.

Output

The node outputs an array of JSON objects, each containing a response field. This field holds the response returned from the Taskt API after executing the script. The structure of the response depends on the Taskt API but generally includes execution results or error messages.

If the node encounters an error during execution and "Continue On Fail" is enabled, the output will contain an error message inside the json object for the corresponding item.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the Taskt API service.
  • Needs an API authentication token (referred to generically as an API key credential) with fields including an authorization key and domain URL.
  • The node uses an internal helper function to replace variables in the script before sending it.
  • Network access to the Taskt API endpoint must be configured properly in the environment where n8n runs.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Malformed or incorrectly base64-encoded scripts may result in errors from the Taskt API.
    • Incorrect variable names or values might cause the script execution to fail or behave unexpectedly.
    • Network connectivity problems can prevent communication with the Taskt API.

  • Error messages:

    • Errors thrown by the Taskt API are captured and either cause the node to fail or are included in the output if "Continue On Fail" is enabled.
    • Typical error messages relate to authentication failure, invalid script format, or server errors.

  • Resolution tips:

    • Verify that the API key and domain URL are correctly set in the node credentials.
    • Ensure the script is properly base64-encoded before input.
    • Double-check variable keys and values for correctness.
    • Confirm network connectivity and firewall settings allow outbound requests to the Taskt API.

Links and References

Discussion