> ## Documentation Index
> Fetch the complete documentation index at: https://trickest.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Building Blocks

> Scripts, tools, and modules as the executable nodes in your workflows.

## Overview

On this page you will learn what building blocks are in Trickest, why they exist, and how they relate to workflows and the Library.

## What are Building Blocks

Building blocks are the **nodes** in your workflows. Each node is one of three types: a **script**, a **tool**, or a **module**. Together they are the executable components that give you a standardized way to run security tooling and custom automation without installing or wiring everything yourself.

## Why They Exist

Nodes solve the usual pain of offensive security tooling: finding tools, installing them, managing dependencies and environments, and chaining them manually. In Trickest, each node runs in a containerized environment with the right runtime and dependencies. You add nodes to a workflow, connect inputs and outputs, and the platform handles execution. You can reuse nodes from the [Library](/docs/library/introduction) or add your own.

## How It Works

Each node wraps a specific script, tool, or process and exposes a consistent interface: configurable parameters (inputs) and one or more outputs (e.g. files, folders, or data). When a workflow runs, the platform executes each node in order, passing outputs from one node to the inputs of the next. You design the workflow; the platform runs it in a repeatable way.

## Building Block Types

<CardGroup cols={2}>
  <Card title="Scripts" icon="code" href="/docs/key-concepts/building-blocks/scripts">
    Python and Bash scripts for custom automation and one-off logic.
  </Card>

  <Card title="Tools" icon="wrench" href="/docs/key-concepts/building-blocks/tools">
    Command-line tools that cover specific security tasks and processes.
  </Card>

  <Card title="Modules" icon="cube" href="/docs/key-concepts/building-blocks/modules">
    Reusable subgraphs that encapsulate end-to-end processes or use cases.
  </Card>
</CardGroup>

## How It Relates

* **Workflows:** Nodes in a workflow are scripts, tools, or modules. The workflow defines the graph; the nodes are the steps. See [Workflows](/docs/key-concepts/workflows).
* **Library:** The Library is where you discover and reuse scripts, tools, and modules as nodes. You add them to your workflows from there or use your own.
* **Runs:** When you run a workflow, each node executes and produces outputs that feed the next node.

## Common Patterns

* Picking scripts or tools from the Library and chaining them as nodes in a workflow
* Using modules to reuse a whole subgraph across multiple workflows
* Passing output from one node (e.g. a tool that finds subdomains) into another (e.g. a tool that probes them)
* Combining custom scripts with existing tools for hybrid automation

## Next Steps

<CardGroup cols={2}>
  <Card title="Navigating the Editor" icon="diagram-project" href="/docs/using-the-app/workflow-and-executions/navigating-the-editor">
    Learn the workflow editor layout and how to add nodes.
  </Card>

  <Card title="Building and Debugging a Workflow" icon="code" href="/docs/using-the-app/workflow-and-executions/building-and-debugging-a-workflow">
    Add and connect nodes, then run and inspect workflows.
  </Card>

  <Card title="Using Workflows From the Library" icon="book" href="/docs/using-the-app/workflow-and-executions/using-workflows-from-the-library">
    Copy workflows and nodes from the Library into your workspace.
  </Card>
</CardGroup>