- Parse different tools outputs to make it compatible with the other tools input
- Extract relevant information from the tool to make it more clear what is important
- Create custom reports, images or files from the other tools outputs
- And much more.
ffuf
output and extract relevant information from it which we covered in Tools section.
Tools Output
In the previous section, we’ve createdffuf
node with certain inputs. Let’s execute it locally first, to check how it’s output looks like.
url
, status
, content-type
, length
, words
, redirectlocation
.
Let’s create a simple python
script which will extract this data, and learn how to use this script in Trickest Platform to parse it whenever we want to brute-force different web server.
Using Scripts in Trickest Platform
Now, let’s take a look how Trickest is handling scripts nodes. If you remember from Tools section, they have their inputs parameters, configurations and file and folder outputs. Scripts are slightly different. Think about Scripts as a little virtual machines that are spinning up and executing the code you provided. They have their own inputs and outputs, and they can be connected to the other nodes as well. In the Left Sidebar, we can search forpython-script
and drag & drop it to the canvas.

Python Script Node example
If you want to use the
file
output from python scripts outputs and connect it to other nodes, that file must be in out/output.txt
pathfile
and folder
inputs and file
and folder
outputs.
Using Scripts to parse ffuf
output
Now, let’s get back to our ffuf
workflow and add python script. We are also going to connect ffuf
output to the python-script
input.

Connecting Python Script to `ffuf`
python-script
node.

Pasting the script
-
For
File
inputs -
For
Folder
inputs
Generated Paths
If we take a look at our particular example, the generated input from
ffuf
is
in/ffuf-1/output.txt
These paths are generated automatically based on the node-id
every node has.In our example ffuf
node has ffuf-1
as node-id
,
and python-script
node has python-script-1
as node-id
.
Changing the script
In our example we need to change path we used to test out the script, to the generated path in Trickest.bash
script.