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

# Workflows

> What workflows are, how they work, and how they relate to runs and nodes.

## Overview

On this page you will learn what workflows are in Trickest, how they work at a high level, and how they relate to runs, nodes, and the rest of the platform.

## What is a Workflow

A workflow is the automation you define by placing and connecting nodes on a canvas. Each node represents a step: a script, tool, or module. Connections between nodes define how data flows from one step to the next. The graph of nodes and connections is your security process.

Workflows exist so you can define repeatable, visual automation instead of wiring tools manually. You get one place to design the process, run it, and inspect what happened.

## How it works

You design a workflow on a canvas by adding nodes and connecting their inputs and outputs. When you run a workflow, the platform executes the nodes according to that graph and records the outcome as a run. Each run captures what each node did. Design, execution, and inspection all live in the same workflow view: you see the same canvas, the list of runs, and the details of any run and its nodes.

The building blocks of nodes (scripts, tools, and modules) are described in [Building blocks](/docs/key-concepts/building-blocks/introduction).

## How it relates

* **Workspaces and projects:** Workflows live in a workspace and optionally inside a project. See [Workspaces & Projects](/docs/key-concepts/workspaces-and-projects).
* **Runs:** A run is one execution of a workflow. One workflow can have many runs; each run is a record of that execution and what each node produced.
* **Nodes:** Nodes are the steps in the graph. They are implemented by scripts, tools, or modules from the [Building blocks](/docs/key-concepts/building-blocks/introduction) and the [Library](/docs/library/introduction).

## Common patterns

* Reusing workflows from the Library as a starting point and adapting them to your needs
* Chaining tools and scripts in a graph to form a repeatable pipeline
* Using modules to encapsulate subgraphs and reuse them across workflows
* Inspecting runs to see what each node did and debug or tune the workflow

## 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 inspect runs.
  </Card>

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

  <Card title="Executing and Scheduling Workflows" icon="clock" href="/docs/using-the-app/workflow-and-executions/executing-and-scheduling-workflows">
    Run workflows on demand with Execute, Smart Execute, or Advanced Execute, or schedule recurring runs.
  </Card>

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