Workflows

A workflow is a saved sequence of blocks. It can run code in seven languages, call saved HTTP endpoints and MCP tools, ask an AI model, branch, and loop. You can start it by hand or with a trigger. Each workflow is one YAML file, and each run gets its own folder.

The course runs in order from Stage 0 to Stage 10. Each stage is a section in the sidebar, and each lesson takes 5–20 minutes.

• 0 · Orientation

  What a workflow is, how to switch Workflows on, and a tour of the page.

• 1 · First workflow

  Build, save, run, and inspect a workflow, then pass a value from one block to the next.

• 2 · Programming model

  How code blocks receive input and publish output: TERMORQ_INPUT, uses, output schemas, ok, Execute step, Code file, and Git file.

• 3 · Seven languages

  The same input/output contract in Bash, PowerShell, Python, C#, Rust, JavaScript, and TypeScript.

• 4 · Connecting blocks

  HTTP endpoints, MCP tools, AI models, and ✦ Autogenerate: reuse saved connections instead of writing clients.

• 5 · Control flow

  Branch with Decision, iterate with Loop, and route with then, break, continue, and disabled nodes.

• 6 · YAML authoring

  Write complete workflow files by hand: root keys, block keys per kind, templates, and validation.

• 7 · Runs & ops

  Run folders, run history, pause and resume, notices and settings, termorq-cli, and troubleshooting.

• 8 · Triggers

  Start workflows automatically: schedule, startup, after another workflow, file change, HTTP, and Telegram.

• 9 · Capture & share

  Turn a terminal session into a workflow draft, then export, import, and share workflows with a team.

• 10 · Capstone

  One HTTP-triggered workflow that uses every runnable block type and all seven languages.