Taskt SL icon

Taskt SL

Perform Taskt operations

Overview

This node allows users to perform operations with Taskt, an automation scripting tool. It sends a user-defined script along with optional variables to a Taskt API endpoint for execution. This is useful in scenarios where you want to automate tasks by running custom Taskt scripts remotely via API calls.

Practical examples include:

  • Automating repetitive desktop or web tasks by sending Taskt scripts dynamically.
  • Integrating Taskt-based automation into larger workflows within n8n.
  • Passing variables to customize the behavior of Taskt scripts at runtime.

Properties

Name Meaning
Script The Taskt script content encoded as a string (expected to be base64 encoded).
Variables A collection of key-value pairs representing variables to be injected into the script.

The "Variables" property allows multiple entries, each with:

  • Variable: The name/key of the variable.
  • Value: The value assigned 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 call
  }
}

If the node encounters an error during execution and is set to continue on failure, it outputs an object with an error message inside the json field.

The node does not output binary data.

Dependencies

  • Requires access to a Taskt API endpoint.
  • Requires an API authentication token (referred to generically as an API key credential).
  • The node expects the Taskt script to be base64 encoded before sending.
  • The node uses HTTP POST requests to communicate with the Taskt API.

Troubleshooting

  • Common issues:

    • Invalid or missing API authentication token will cause authorization failures.
    • Improperly base64-encoded script content may lead to errors or unexpected behavior.
    • Network connectivity issues to the Taskt API domain can cause request failures.
    • Incorrect variable names or values might cause the Taskt script to fail during execution.

  • Error messages:

    • Errors thrown by the node typically contain the message from the underlying HTTP request or script processing.
    • If the node is configured to stop on failure, these errors will halt workflow execution.
    • To handle errors gracefully, enable "Continue On Fail" in the node settings.

Links and References

Discussion