Getting started
Knowledge hub
- Overview
-
-
- 34 M Wordlist Subdomain Brute Force
- Asn Based Network Scan
- Asset Discovery and Vulnerability Scanning
- Custom Subdomain Brute Force Wordlist From Ip Ranges
- Enumerate Cloud Resources
- Full Subdomain Enumeration
- Get Ips and Cnames
- Getdns
- Github Recon and Scanner
- Hostnames S3 Bucket Finder
- Simple Content Discovery
-
-
- amass
- anew
- apkurlgrep
- assetfinder
- cent
- cero
- cewl
- cloudenum
- crosslinked
- dnsdumpster-dns-lookup
- dnsdumpster-host-search
- dnstwist
- dnsvalidator
- dsieve
- dumpsterdiver
- eyeballer
- ffuf
- find-gh-poc
- findomain
- gau
- generate-yaml-report
- get-asn-prefixes
- get-trickest-output
- gf
- github-subdomains
- goaltdns
- gospider
- gotator
- hakcheckurl
- httprobe
- httpx
- infoga
- ipinfo
- jldc-subdomains
- katana
- mapcidr
- mass-linkfinder
- masscan
- massdns
- meg
- mksub
- naabu
- notify
- nrich
- nuclei
- oneforall
- puredns
- pymeta
- s3scanner
- securitytrails-subdomains
- spiderfoot
- sslyze
- subdomainizer
- subfinder
- tlsx
- uncover
- unfurl
- uro
- vita
- webanalyze-1
- webanalyze
- x8
Tutorials
- Creating a Workflow
- Downloading a Result
- Executing a Workflow
- How Do Machines Work
- Keeping Track of a Run
- Navigating in Workflow Editor
- Overview
- Saving a Workflow and History
- Scheduling a Workflow
- Using Workflows From Library
Concepts
Nodes
Nodes are building blocks/individual units of computation wired together to form a workflow - a DAG of processes.

Nodes interconnected to form a workflow
Nodes Library
Trickest platform provides several types of ready-to-go nodes to be used in workflows:
- Tools - most advanced ready-to-go community tools,
- Scripts - advanced ready-to-go customizable bash scripts made by Trickest,
- Splitter - util node for executing a specific set of connected nodes within a workflow multiple times in batches, in parallel.
Node I/O and connections
Nodes are automated actions with the purpose of performing specific tasks consuming data (inputs), and producing data (outputs).

Node structure
Nodes can be interconnected via data dependencies defined between their inputs and outputs. Data is passed from one node’s output to another node’s input.
Inputs
Each node has a predefined set of inputs that vary from node to node. At least one input needs to be set. The value of an input can be passed from the output of another node or stubbed (hardcoded).
Inputs have a few important properties:
- They are named.
- They are typed. Several types are provided:
INPUT TYPE | DESCRIPTION |
---|---|
String | String input's value is a simple text value (e.g. uber.com value for --domain input of amass tool node). |
Boolean | Boolean input is also known as a flag in the hacking community. Value is true for activating given behavior. |
File | File input's value can be either file uploaded to Trickest Platform, or URL of the publicly available file (e.g. https://raw.githubusercontent.com/cujanovic/goaltdns/master/words.txt ). |
Folder | Folder input's value is URL of publicly available GIT repository. |
Outputs
Output is the result of a node execution, ready to be downloaded or used as an input of other nodes.
Two types of output are provided - file and folder. The type of output that is produced, is determined by the logic of the node itself.
File | By default, output is output.txt file on out/output.txt path. |
Folder | By default, output is a folder on out/ path containing output.txt file. |
Connections
Nodes are interconnected via data dependencies defined between their inputs and outputs. Data is passed from one node’s output to another node’s input.
Get a Video Demo
Fill out and submit this form to receive an in-depth video demo of the Trickest platform.
Talk To Sales
Fill out the form and we'll get back to you about any questions you have on our products, services, pricing, or scheduling a demo.