loading
Loading content
loading
Utilities
Write strings to a file.
overview
string-to-file does one job: it takes a string and writes it to a file. In a workflow where most nodes read and write files, this is the glue that turns an inline value, a single domain, a config snippet, or a small wordlist, into a file the next node can consume.
Because it is so small, it shows up wherever a node expects a file but you only have text. Seed a scan with one target, hand a tool a one-line config, or paste a short list into the graph without leaving to build the file by hand. Multi-line text becomes a multi-line file, so a handful of hosts or paths is a wordlist in one node.
On Trickest, string-to-file is a Utilities node that takes a string and emits both a FILE and a FOLDER. Place it upstream of any tool whose input is a FILE, such as nuclei's -l, masscan's -il, or ffuf's -input-file, so the literal you typed becomes a real artifact the rest of the workflow can pass around.
source github.com/trickest
use cases
Write a single domain, URL, or IP to a file so a tool that reads its targets from a file (nuclei -l, masscan -il) runs without a separate input node.
Turn a short config, header block, or template into a file for a node that reads its settings from disk, without checking a file into a repo.
Paste a handful of paths or words as a multi-line string to drive ffuf or a fuzzer without sourcing and mounting a full wordlist.
Convert a typed value into a FILE artifact so downstream file-consuming nodes connect cleanly in the graph instead of expecting a raw string.
reference
| Name | Type | Flag | Description |
|---|---|---|---|
| string | STRING | · | The string to write to the output file. Multi-line text is written line for line, so it doubles as a quick target list or wordlist. |
Showing key inputs. string-to-file exposes 1 inputs in total.
example
# write a small seed list to a file the next node reads (nuclei -l, ffuf -input-file)string-to-file "example.comapp.example.comapi.example.comstaging.example.com198.51.100.10198.51.100.11203.0.113.5"$ cat out.txtexample.comapp.example.comapi.example.comstaging.example.com198.51.100.10198.51.100.11203.0.113.5guidance
Reach for string-to-file whenever a downstream node needs a FILE but you only have a literal string. It is plumbing, not a scanner. For combining or deduplicating many files instead of writing one, use a list-handling utility like anew.
Appends only new, unique lines to a file. Use it to grow a list; string-to-file creates one from a literal.
Another small workflow utility. It validates a condition rather than materializing a string as a file.
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 string feeds string-to-file, which writes it to disk as a file artifact the rest of the workflow can read.
Facts on this page come from the live Trickest tool library.