Taskt SL icon

Taskt SL

Perform Taskt operations

Overview

This node allows users to execute Taskt scripts by sending them to a Taskt API endpoint. It is designed to perform automation or scripting tasks remotely via the Taskt platform. Users can provide a script along with variables that will be dynamically replaced before execution. This node is useful for automating workflows that require running custom Taskt scripts, such as robotic process automation (RPA) tasks, data processing, or system integrations.

Practical examples include:

  • Running a Taskt script that automates form filling on a website.
  • Executing a script that processes files and returns results.
  • Triggering complex automation sequences defined in Taskt from within an n8n workflow.

Properties

Name Meaning
Script The Taskt script code to execute. This is a string containing the script instructions.
Variables A collection of key-value pairs where each key is a variable name used in the script, and the value is the string to replace it with before execution. Multiple variables can be added.

Output

The node outputs an array of JSON objects, each corresponding to one input item processed. Each output object has a json field containing:

  • response: The response returned from the Taskt API after executing the script. This typically includes the result or status of the script execution.
  • In case of failure (if "Continue On Fail" is enabled), the output contains an error message describing what went wrong.

No binary data output is produced by this node.

Dependencies

  • Requires access to a Taskt API endpoint, which must be configured with appropriate credentials including an authentication key and domain URL.
  • The node expects a credential providing at least an API key (authKey) and the API domain (domain).
  • Uses an internal helper function to replace variables in the script before sending it to the API.
  • Requires network connectivity to the Taskt service.

Troubleshooting

  • Common issues:
    • Invalid or missing API credentials will cause authentication failures.
    • Malformed or incorrect script syntax may lead to errors returned by the Taskt API.
    • Network issues or incorrect API domain configuration can cause request failures.
  • Error messages:
    • Errors thrown during the HTTP request are caught and either cause the node to fail or return an error object if "Continue On Fail" is enabled.
    • Typical error messages include authentication errors, script parsing errors, or connection timeouts.
  • Resolution tips:
    • Verify that the API key and domain are correctly set in the node credentials.
    • Ensure the script syntax matches Taskt's expected format.
    • Check network connectivity and firewall settings.
    • Use "Continue On Fail" cautiously to handle partial failures gracefully.

Links and References

Discussion