How does put-trickest-files differ from get-trickest-files?

put-trickest-files writes into storage; get-trickest-files reads back. Use diff-trickest-files between runs to detect changes.

Why use the --dependency input?

It forces this node to run after another. In a diff pipeline, connect --dependency to the get or diff node so previous results are read before this upload overwrites them.

Can I rename a file on upload?

Yes, with --file-name, but only alongside --input-file. It has no effect on --input-folder, which keeps each file's original name.

What does --fail-on-error change?

With it on, errors such as an invalid token fail the node. Without it, the input can pass through without uploading.

Updated Jul 14, 2026

Utilities

Persist workflow output in Trickest storage

Write workflow results into Trickest file storage.

Persist results across scheduled runs Order an upload after a diff Archive a whole folder of scan output

overview

What put-trickest-files does

put-trickest-files is the write side of Trickest file storage. Pass --input-file or --input-folder plus --token or --token-file so results survive past a single run.

Set --file-name for a stable name with --input-file. Wire --dependency so a get or diff reads old results before this node overwrites them. --fail-on-error stops a bad token from silently skipping the write.

Trickest provides this as a managed Utilities node at the end of pipelines that need cross-run state. Prefer get-trickest-files to read, diff-trickest-files to compare, and export-to-azure-blob for external storage.

use cases

Where put-trickest-files fits

Persist results across scheduled runs

Upload a results file at the end of a workflow so the next scheduled run can read it back and diff against it for change detection.

Order an upload after a diff

Use the --dependency input to guarantee a diff or get-trickest-files node reads the previous results before this node overwrites them.

Archive a whole folder of scan output

Point --input-folder at a directory so every file from a scan stage lands in storage in one node, ready for the next run to pull back.

Rename an upload on the way in

Set --file-name so the stored file lands with a stable, predictable name regardless of the producing node's output name.

reference

put-trickest-files inputs and flags

7 inputs

Name	Type	Flag	Description
input-file	FILE	--input-file	File to upload.
input-folder	FOLDER	--input-folder	Folder of files to upload.
token	STRING	--token	Trickest authentication token.
token-file	FILE	--token-file	Trickest authentication token file.
file-name	STRING	--file-name	Rename the uploaded file (with --input-file only).
dependency	FILE	--dependency	A node that must run before this one, for ordering against a diff or get.
fail-on-error	BOOLEAN	--fail-on-error	Fail on errors such as an invalid token instead of passing input through.

Showing key inputs. put-trickest-files exposes 7 inputs in total.

example

Run put-trickest-files

put-trickest-files · command

# persist a scan-results file into Trickest storage at the end of a runput-trickest-files --token-file /tmp/trickest-token --input-file results.txt --file-name subdomains.txt --fail-on-error

sample output

[*] Loading input: results.txt (2.4 KB)[*] Authenticating with Trickest file storage[+] Uploading results.txt as subdomains.txt[+] Upload complete: subdomains.txt[*] File available in storage for the next run[+] 1 file uploaded, 0 failed

guidance

Choosing put-trickest-files

Use put-trickest-files to save workflow output into Trickest storage so a later run can read it back. Pair with get-trickest-files to read and diff-trickest-files to detect what changed across runs.

get-trickest-files

Read half of the pair. Pulls previously stored files back into a workflow.

diff-trickest-files

Compares current results with stored ones to surface what is new between runs.

export-to-azure-blob

Ships output to Azure Blob storage instead of Trickest file storage.

faq

put-trickest-files questions

Wire the file into --input-file and supply --token or --token-file. For a whole directory, use --input-folder instead.

Run put-trickest-files yourself

A scan-results file feeds put-trickest-files, which uploads it into Trickest file storage so a later run can read it back and diff against it.

Open put-trickest-files in the library Build a workflow with it

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