loading
Loading content
loading
Utilities
Upload a file or files into your Trickest file storage.
overview
put-trickest-files takes a file or folder produced earlier in a workflow and uploads it into your Trickest file storage, so results survive past a single run. It authenticates with a token, accepts either --input-file or --input-folder, and can rename a single upload with --file-name. It is the write half of Trickest's storage pair: get-trickest-files reads, put-trickest-files writes.
The point is carrying state between scheduled runs. Persist a results file when a workflow finishes, and the next run reads it back to diff against, which is how continuous attack-surface monitoring reports only what changed. The --dependency input orders this node after a diff or a get, so old results are read before this node overwrites them.
If an upload fails, --fail-on-error stops the node instead of passing the input straight through, which keeps a bad token from silently skipping the write. Place put-trickest-files at the end of any pipeline whose output you want to keep.
use cases
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.
Use the --dependency input to guarantee a diff or get-trickest-files node reads the previous results before this node overwrites them.
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.
Set --file-name so the stored file lands with a stable, predictable name regardless of the producing node's output name.
reference
| 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
# 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
Use put-trickest-files to save a workflow's output into Trickest storage so a later run can read it back. Pair it with get-trickest-files, which reads, and use diff-trickest-files between them to detect what changed across runs.
The read half of the pair. Pulls previously stored files back into a workflow.
Compares the current results with stored ones to surface what is new between runs.
Ships output to external Azure Blob storage instead of Trickest's own file storage.
faq
related
Import, export, and link workflow data with Airtable.
Decode Android APK files into smali sources and resources.
Check a file's values against conditions and exit with a matching code.
Extract all hosted zones from AWS Route53.
Output file lines by batch size, given START_LINE and END_LINE.
Extract a batch range from a file's lines or a folder's files, with parallel processing.
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.