Taskt SL icon

Taskt SL

Perform Taskt Operations

Overview

This node integrates with the Taskt automation platform by sending scripts to be executed remotely. It allows users to define a script and variables that will be injected into the script before execution. The node supports two input methods for providing variables: either as individual key-value pairs ("One By One") or as a JSON block.

Common scenarios where this node is useful include automating repetitive tasks, running custom scripts on remote systems via Taskt, or integrating Taskt workflows into an n8n automation pipeline. For example, you could dynamically generate a script with user-specific data and execute it on a Taskt server to perform UI automation or system operations.

Properties

Name Meaning
Input Method Choose how to provide variables to the script: "Json Block" (a JSON string) or "One By One" (individual variable entries).
Script The Taskt script content to execute. Variables can be embedded and replaced dynamically.
Variables When using "One By One" input method, specify multiple variables as key-value pairs to inject into the script. Default example variable is v_Message.
Variables (JSON) When using "Json Block" input method, provide all variables as a single JSON string object.

Output

The node outputs an array of items, each containing a json field with a response property. This response holds the raw response returned from the Taskt API after executing the script. The exact structure depends on the Taskt API's response but typically includes execution results or error information.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to a Taskt API endpoint.
  • Needs an API authentication token (referred generically as an API key credential) configured in the node credentials.
  • Uses HTTP POST requests to send base64-encoded script data to the Taskt server.
  • Relies on helper functions to replace variables in the script and encode the script in base64.

Troubleshooting

  • Common issues:
    • Invalid or missing API authentication token will cause request failures.
    • Malformed JSON in the "Variables (JSON)" input will cause parsing errors.
    • Script syntax errors or invalid variable placeholders may lead to unexpected Taskt execution errors.
  • Error messages:
    • If the Taskt API returns an error, it will be captured and included in the output under error.
    • Node operation errors will indicate the item index causing failure unless "Continue On Fail" is enabled.
  • Resolutions:
    • Verify API credentials and endpoint URL.
    • Ensure JSON strings are valid and properly formatted.
    • Test scripts independently in Taskt to confirm correctness before use in the node.

Links and References

Discussion