Utilities
Persist workflow output in Trickest storage
Write workflow results into Trickest file storage.
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
| 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
# 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[*] 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 failedguidance
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
related
More Utilities tools
browser-fetch
Headless Chromium render: requested URL, final URL, status, and title next to the page.
cewl
Spider a URL and return a wordlist for password crackers.
csvkit
SQL on one CSV. The table name is the file stem.
dnsgen
Wordlist and mined-word subdomain permutation.
duckdb
In-process SQL on CSV, JSON, and Parquet. No server.
edge-tts
Microsoft Edge neural speech from text or a script file. No API key.
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.
Facts on this page come from the live Trickest tool library.