Updated Jul 15, 2026

Utilities

Pull a workflow node's results to disk

Deprecated. Downloaded Trickest workflow node outputs by id.

Agent

overview

What get-trickest-output does

get-trickest-output downloaded one workflow node's results to a local folder. Select the run with -wf and -wf_version, the producer with -node, and authenticate with -token or -config.

The library marks it deprecated. It does not track newer export paths, so new graphs should not wire it in. Keep this page for reading older workflows that still call it.

Trickest lists it as a legacy Utilities node. Prefer the maintained Trickest CLI or get-bucket-data for current exports. Add -all only when every matching run must land on disk, not just the latest.

use cases

Where get-trickest-output fits

Pull a workflow node's results to disk

Download the output files a specific node produced so you can grep, diff, or hand them to a local script. This is the core job the node did before the maintained CLI took it over.

Grab every run of a node, not only the latest

With -all, download the output of every matching run of a node rather than the single most recent one, which helps when comparing results across executions or auditing a pipeline's history.

Read a legacy workflow that references it

If an older workflow still wires in get-trickest-output, this page explains what the node did and what each input meant so you can follow the graph.

Migrate the download step to the Trickest CLI

Find where a workflow fetched outputs by node id, then swap that step for the maintained Trickest CLI or an export node before you re-run.

reference

get-trickest-output inputs and flags

6 inputs
NameTypeFlagDescription
node_idSTRING-nodeId of the workflow node whose output you want to download.
tokenSTRING-tokenTrickest API token, taken from your dashboard account settings.
config-fileFILE-configYAML config file that holds the API token, so you do not pass it on the command line.
workflow_idSTRING-wfId of the workflow the target node belongs to.
workflow_versionSTRING-wf_versionName of the workflow version to read the node from.
all-outputsBOOLEAN-allDownload the output of every matching run, not only the most recent.

Showing key inputs. get-trickest-output exposes 6 inputs in total.

example

Run get-trickest-output

get-trickest-output · command
# download the most recent output of one workflow node into ./outputget-trickest-output -token $TRICKEST_TOKEN -wf recon-pipeline -node httpx-probe
sample output
Fetching output for workflow "recon-pipeline" (version v1.4)Node httpx-probe: downloading most recent output  output/httpx-probe/hosts.txt   ok  output/httpx-probe/urls.txt    okNode httpx-probe: 2 files saved to ./output/httpx-probeDone: outputs written under ./output

guidance

Choosing get-trickest-output

Do not use get-trickest-output in new work. It is deprecated; the Trickest CLI and platform export paths cover the same job. Open this page only to understand legacy workflows that still call it.

trickest-cli

Maintained CLI for running workflows and pulling outputs. Prefer this over the deprecated node.

get-bucket-data

Fetches stored data from a bucket when results already sit outside a node-id download.

faq

get-trickest-output questions

No. The library marks it deprecated. It may still run against older workflows, but the Trickest CLI and platform export paths receive updates. Keep new work on those.

Run get-trickest-output yourself

A node id feeds get-trickest-output, which downloads that node's results into a folder. The node is deprecated, so prefer the Trickest CLI for new workflows.

Facts on this page come from the live Trickest tool library.