Taskt SL icon

Taskt SL

Perform Taskt operations
Join our community

Overview

This node allows users to execute Taskt scripts by sending them to a Taskt API endpoint. It is designed to facilitate automation workflows where Taskt scripting is used for robotic process automation (RPA) or other scripted tasks. Users can input a script along with variables, which the node processes and sends to the Taskt service for execution.

Common scenarios include:

  • Automating repetitive desktop tasks via Taskt scripts.
  • Integrating Taskt-based RPA into broader n8n workflows.
  • Dynamically modifying Taskt scripts with variables before execution.

For example, a user might prepare a Taskt script that automates data entry in an application, then use this node to run that script with different variable values depending on the workflow context.

Properties

Name Meaning
Script The Taskt script code to be executed.
Variables A collection of key-value pairs representing variables to replace or inject into the script before execution. Each variable has:
- Variable: The name of the variable in the script.
- 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 is:

{
  "response": {
    // Response data from Taskt API, typically including execution results or status
  }
}

No binary data output is produced by this node.

Dependencies

  • Requires access to a Taskt API endpoint, configured via credentials that provide:
    • An authentication key (AuthKey) for API authorization.
    • The domain URL of the Taskt API.
  • Uses helper functions to:
    • Replace variables in the script text.
    • Encode the script in base64 before sending.
  • Requires network connectivity to the Taskt API service.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Malformed or incorrect Taskt scripts may result in errors from the API.
    • Network connectivity problems can prevent the node from reaching the Taskt service.

  • Error messages:

    • Errors thrown during the request are caught and either cause the node to fail or, if "Continue On Fail" is enabled, return an error object in the output.
    • Typical error messages relate to authentication failure, invalid script data, or HTTP request issues.

  • Resolution tips:

    • Verify that the API key and domain URL are correctly set in the node credentials.
    • Ensure the script syntax is valid and variables are properly defined.
    • Check network access and firewall settings to allow outbound requests to the Taskt API.

Links and References

Discussion