What is a workflow?

A workflow is a sequence you’ll want to run again. In Termorq it is one YAML file. The Editor tab shows it as a canvas and the YAML tab shows the same file as text. Changes on one tab appear on the other, because both edit the same file.

The vocabulary

How data flows

flowchart LR
  T["Trigger<br/>trigger.text"] --> A["Code block<br/>uses: trigger.text"]
  A -->|"steps.a.message"| B["HTTP block<br/>{{ steps.a.message }}"]
  B -->|"steps.b.status"| C{"Decision<br/>steps.b.status == 200"}
  C -->|when| D["AI block"]
  C -->|else| E["Code block"]

Data moves forward only through declared properties:

• A code block lists the paths it needs under uses. At run time it reads them from a JSON file whose path is in TERMORQ_INPUT.
• An HTTP, MCP, or AI block uses {{ steps.<id>.<property> }} templates in its fields.
• Every block publishes properties. A later block reads them as steps.<block id>.<property>.

Each code block runs as its own process. A shell variable set in one block doesn’t exist in the next one. To pass a value on, publish it as a property.

Workflows are not runbooks

Termorq also has collection runbooks, Markdown runbooks, and repo runbooks. These are separate features, and nothing in this course changes them.

Reference: Build a workflow

Enable Workflows and install runtimes

Steps

1. Open Settings → Experimental.
2. Turn on Workflows. It is off by default.
3. Open the page with Cmd+Shift+G (macOS) or Ctrl+Shift+G (Windows/Linux). You can also open the jump list with Ctrl+J and choose Workflows, or type @flow.

If you later turn the flag off, Termorq hides the page’s entry points and workflow settings. A workflow that is already open stays open until you leave it.

Check your runtimes

Termorq doesn’t bundle language runtimes. The code runner uses whatever is installed on your computer. Run these commands in a Termorq terminal tab:

bash --version | head -1
jq --version            # used by Bash JSON examples
pwsh --version          # PowerShell
python3 --version
dotnet --version        # needs 10.0 or later for C#
rustc --version         # needs Rust 2024 edition support
node --version          # 22.6+ runs TypeScript natively

bash --version          # Git Bash or WSL exposed on PATH
jq --version
pwsh --version
python --version
dotnet --version
rustc --version
node --version

Reference: Node types and code languages

Tour the Workflows page

The list

• The All, Yours, Included, and Workspace chips filter by source.
• The trigger pills filter by trigger type: Manual, Schedule, At startup, After workflow, File change, HTTP request, Telegram.
• Each row shows the trigger, last edited and run times, run count, disk use, and the latest result. Its actions are Runs, Edit, Copy, Export, and Delete. Delete appears when you hover over or focus the row.
• Included workflows are read-only. Use Copy to make your own editable version. A copy starts with its triggers paused.

The editor

Keyboard and navigation

Runs keep going after you leave the page. When a run is in progress, the footer shows a chip such as 1 workflow running. Click it to go back to the page.

Reference: Build a workflow