How does --partial-name-match work?

With --partial-name-match on, a stem like subdomains.txt retrieves every stored file whose name contains it, such as trickest.com-subdomains.txt. Useful for gathering per-target copies in one node.

What happens if a file is missing or the token is invalid?

By default the node writes an empty output and continues. Set --fail-on-error to stop and surface the error when a downstream stage requires the file.

How do I authenticate the fetch?

Pass --token inline or point --token-file at a token file. Inside a Trickest workflow the platform usually injects auth, so you rarely set these by hand.

How do I wait for an upload before fetching?

Set --dependency to the uploading node. The fetch runs only after that node finishes, so the download never races the producer.

Updated Jul 14, 2026

Utilities

Bring stored files into a workflow run

Pull named files from Trickest file storage into a workflow.

Carry results between workflows Pull a shared wordlist or scope file Collect files by partial name

overview

What Get Trickest Files does

Get Trickest Files is the read side of Trickest file storage. Pass --file-names and the node downloads each match as folder and file outputs later stages can read.

Enable --partial-name-match when one stem should collect every stored match, such as subdomains.txt pulling host-prefixed copies. Use --dependency so a fetch waits on the upload that produces it.

Trickest provides this as a managed Utilities node for cross-run state. Prefer Put Trickest Files to upload, Diff Trickest Files to compare against storage, and Trickest Output for a whole run rather than named files.

use cases

Where Get Trickest Files fits

Carry results between workflows

Store a list of live hosts or resolved subdomains from one run, then fetch it by name in a later workflow so the second run builds on the first without recomputing the surface.

Pull a shared wordlist or scope file

Keep a curated wordlist or in-scope target list in file storage and retrieve it at the start of a workflow, so every run reads the same maintained source instead of an inline copy.

Collect files by partial name

Enable partial-name matching to grab every stored file that ends in a common suffix, gathering per-target outputs like trickest.com-subdomains.txt across many hosts into one folder in a single node.

Wait for an upstream upload before fetching

Set a dependency so the fetch only runs after the producing node has written its output to storage, keeping a download from racing ahead of the upload it relies on.

reference

Get Trickest Files inputs and flags

6 inputs

Name	Type	Flag	Description
file-names	STRING	--file-names	Names of the files to get, separated by commas.
token	STRING	--token	Trickest authentication token.
token-file	FILE	--token-file	File holding your Trickest authentication token, used in place of an inline token.
partial-name-match	BOOLEAN	--partial-name-match	Get all files whose name contains the given value, so subdomains.txt matches trickest.com-subdomains.txt.
dependency	FILE	--dependency	Force a node to run before this one, for example to wait for an upload to finish before downloading.
fail-on-error	BOOLEAN	--fail-on-error	Fail on errors such as an invalid token. Without it, an error writes an empty output file instead.

Showing key inputs. Get Trickest Files exposes 6 inputs in total.

example

Run Get Trickest Files

Get Trickest Files · command

# fetch every stored file whose name contains subdomains.txttrickest-files --file-names subdomains.txt --partial-name-match --fail-on-error --token-file /root/.trickest/token

sample output

[trickest-files] reading token from /root/.trickest/token[trickest-files] querying file storage for: subdomains.txt[trickest-files] partial-name-match enabled[trickest-files] matched 3 file(s)  example.com-subdomains.txt      128 lines  example.net-subdomains.txt       94 lines  example.org-subdomains.txt       61 lines[trickest-files] wrote 3 file(s) to output/

guidance

Choosing Get Trickest Files

Use Get Trickest Files when a workflow needs a file already in Trickest storage, from a prior run or a maintained source. Prefer Put Trickest Files to upload, Diff Trickest Files to detect changes, and Trickest Output for an entire run's artifacts.

Put Trickest Files

Write side of the pair. Uploads files into storage so a later run can fetch them here.

Diff Trickest Files

Compares an input against a stored file for change detection. Does not only retrieve.

Trickest Output

Downloads a whole workflow run's output, not named files from file storage.

faq

Get Trickest Files questions

Set --file-names to a comma-separated list. The node pulls each file into the workflow as folder and file outputs. For an entire run instead of named files, use Trickest Output or the run page download.

Run Get Trickest Files yourself

A file name feeds Get Trickest Files, which pulls a stored host list from file storage and passes it to httpx for live probing before the results land as an output.

Open Get Trickest Files in the library Build a workflow with it

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