Overview
On this page you will learn what script nodes are in Trickest, how they work, and how they relate to other building blocks and the Library.What is a Script Node
A script node is a containerized environment that runs code you provide. It accepts file and folder inputs and produces file and folder outputs. The same output can be used as a file or a folder depending on how the next node consumes it. Scripts let you add custom logic, parsing, and automation inside a workflow without installing runtimes yourself.Script Types
Trickest supports four script types:- Bash – Shell scripts for quick transformations and glue logic
- Python – For richer parsing, data handling, and integration logic
- Go – For compiled, performant custom code
- Node – JavaScript/Node.js for scripting and tooling
Why Scripts Exist
Scripts extend and automate what tools and modules do. They are used to parse or transform tool output so it fits another tool’s input, extract the information that matters, and produce custom reports, files, or data. Because they run in a container with a known runtime, you avoid “works on my machine” issues and get repeatable execution in the workflow.How It Works
You write your script in one of the supported types (Bash, Python, Go, or Node). You define script arguments; these become node inputs that you can wire from other nodes or set manually. The platform builds the right command for the engine and executes it inside the script’s container. Inputs arrive as files or folders at known locations; your script reads them and writes outputs to the expected paths so the next node can consume them. You can write your own scripts or use preset scripts from the Library, which are ready to drop into a workflow and customize.How It Relates
- Building blocks: Scripts are one of the three node types (scripts, tools, modules). See Introduction.
- Tools: Tools are pre-packaged command-line programs; scripts are code you write or reuse. Both are nodes with file/folder inputs and outputs and can be chained in a workflow.
- Modules: Modules are reusable subgraphs of nodes; a script is a single node. You can use script nodes inside a module.
- Workflows: Scripts run as nodes in a workflow. They receive data from upstream nodes and pass results downstream. See Workflows.
Common Patterns
- Parsing or filtering tool output (e.g. JSON) so it matches the input format expected by the next tool
- Extracting specific fields or lines from large outputs to reduce noise
- Generating custom reports, summaries, or derived files from tool results
- Chaining a script between two tools to adapt data shape or format
- Using a Library script as a starting point and adjusting arguments for your workflow