---
title: "Workflows"
canonical: https://trickest.com/docs/key-concepts/workflows
description: "Understand the workflow graph, execution dependencies, and the difference between an editable workflow and a run."
---

# Workflows

## What is a Workflow

A **workflow** is a graph of connected nodes on the canvas. Tools and scripts perform work; modules contain reusable groups of nodes. Connections specify which output supplies an input on another node.

For example, a discovery tool can produce hostnames, a script can filter them, and a second tool can inspect the filtered list. You configure the graph once and run it again with new inputs.

## How it works

Nodes execute when their dependencies are ready. Independent branches can run in parallel when the fleet has capacity. A connection defines data flow; it does not convert the file's contents into the format a downstream tool expects.

Use the workflow header to move between its canvas and related views such as **Database**, **App**, and **Files**, when available. These views keep the workflow context. The runs sidebar lets you inspect a particular execution.

<Frame editorial darkSrc="https://res.cloudinary.com/db14crach/image/upload/www/docs/v2-ui-2026-10-01/editor/workflow-views-dark-ddd5e7a70ca4" caption="The workflow header keeps related views beside the workflow name. Available views depend on access and enabled features.">
  <img src="https://res.cloudinary.com/db14crach/image/upload/www/docs/v2-ui-2026-10-01/editor/workflow-views-84d35bda753d" alt="Workflow header with controls for switching between the canvas, database, apps, and files." />
</Frame>

## Workflow versus run

| Workflow | Run |
|---|---|
| The editable definition of nodes, connections, and configuration. | A record of one execution using a particular configuration. |
| Changes affect a subsequent execution. | A past run keeps the configuration it used. |
| Can be copied and adapted for another purpose. | Contains execution status, task logs, and produced files. |

While viewing a run snapshot, node configuration is read-only. Return to the editable workflow to make changes. Running a single node and running the whole workflow are different actions; review the selected scope before starting.

A **Completed** status tells you about execution. It does not prove the output contains the records you expected, or that a Live Table imported them successfully. Inspect representative files, logs, and table data when validating a workflow.

## How it relates

- **Spaces and projects** organize workflow definitions and access.
- **Nodes** define the operations and their inputs.
- **Fleets** provide the machines that execute jobs. More nodes do not necessarily mean more machines running at once.
- **Live Tables** store configured structured outputs for querying across runs. They are not created for every output automatically.

## Common patterns

Start with a Library workflow, copy it into your space, configure its inputs, and inspect a small run before scheduling repeated execution. Move repeated groups of nodes into [modules](/docs/key-concepts/building-blocks/modules) when several workflows need the same process.

## Next Steps

- [Navigate the editor](/docs/using-the-app/workflow-and-executions/navigating-the-editor).
- [Build and debug a workflow](/docs/using-the-app/workflow-and-executions/building-and-debugging-a-workflow).
- [Execute and schedule workflows](/docs/using-the-app/workflow-and-executions/executing-and-scheduling-workflows).
- [Inspect runs and restore versions](/docs/using-the-app/workflow-and-executions/working-with-runs).

---
_Markdown source of https://trickest.com/docs/key-concepts/workflows._