Taskt SL icon

Taskt SL

Perform Taskt Operations

Overview

This node integrates with the Taskt automation platform, allowing users to execute Taskt scripts directly from n8n workflows. It supports two input methods for providing script variables: either as individual key-value pairs ("One By One") or as a JSON block. The node processes each input item by injecting the specified variables into the Taskt script, encoding it, and sending it to the Taskt API endpoint for execution.

Common scenarios include automating repetitive tasks that are supported by Taskt scripts, such as UI automation, data entry, or system operations, triggered within an n8n workflow. For example, a user might automate form filling on a website by passing dynamic values from previous workflow steps into a Taskt script.

Properties

Name Meaning
Input Method Method to provide variables to the script. Options: "Json Block" (all variables as JSON) or "One By One" (individual variable entries).
Script The Taskt script code to be executed. Variables will be injected into this script before sending.
Variables (Shown only if Input Method is "One By One") A collection of variable name-value pairs to inject into the script. Each variable has a "Variable" name and its corresponding "Value".
Variables (JSON) (Shown only if Input Method is "Json Block") A JSON string representing all variables to inject into the script.

Output

The node outputs an array of items where each item's json field contains a single property:

  • response: The response returned from the Taskt API after executing the script. This typically includes the result or status of the script execution.

No binary data output is produced by this node.

Dependencies

  • Requires an active Taskt API endpoint and a valid API authentication key.
  • The node expects credentials containing at least:
    • An API domain URL for the Taskt service.
    • An authentication key used in the request header.
  • Uses helper functions from an external module (scriptModify) to:
    • Replace variables inside the Taskt script.
    • Convert JSON variables into a list format.
    • Encode the script content to base64 before sending.
  • Requires network access to the Taskt API endpoint.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Malformed JSON in the "Variables (JSON)" property can cause parsing errors.
    • If the script contains syntax errors or invalid variable placeholders, the Taskt API may reject the request or return an error.
    • Network connectivity issues to the Taskt API endpoint will cause request failures.
  • Error messages:

    • Errors thrown during the HTTP request to the Taskt API will be reported with their message. If "Continue On Fail" is enabled, the error details will be included in the output; otherwise, the node execution will stop.
    • Parsing errors for JSON variables will likely throw exceptions before the request is made.
  • Resolution tips:

    • Verify API credentials and endpoint URL.
    • Validate JSON syntax when using the JSON block input method.
    • Test the Taskt script independently to ensure correctness.
    • Enable "Continue On Fail" to handle partial failures gracefully.

Links and References

Discussion