Windmill · Controlled Vocabulary
Windmill Vocabulary
Domain vocabulary for Windmill, the open-source developer platform and workflow engine for scripts, flows, schedules, and internal tools. Covers core concepts in workflow automation, job execution, resource management, and platform administration.
16 Terms
Updated 2026-05-03
Windmill Vocabulary is a controlled vocabulary published by Windmill on the APIs.io network, defining 16 terms.
Defined terms include Script, Flow, Job, Workspace, and Resource.
A controlled vocabulary pins the words an API’s schemas, parameters and documentation use to one agreed definition each — the shared language a human or an agent needs to read the API the same way its authors do.
Terms
Script
A reusable unit of code in Windmill, written in TypeScript (Deno/Bun), Python, Go, PHP, Bash, C#, SQL, or Rust. Scripts can be run directly, triggered by schedules, or composed into flows.
Flow
A visual, multi-step workflow in Windmill that chains scripts and operations together. Flows support branching, loops, error handling, and approval steps. Equivalent to workflow orchestration in tools like Airflow or Temporal.
Job
A single execution instance of a script or flow in Windmill. Jobs are either queued (waiting to execute), running, or completed. Each job has a unique ID and stores its arguments, results, and execution metadata.
Workspace
An isolated environment in Windmill containing its own scripts, flows, resources, variables, schedules, and users. Similar to a project or organization namespace.
Resource
A named, typed credential or configuration object stored in Windmill (e.g., a database connection, API key, or cloud credentials). Resources are referenced by scripts and flows using their path.
Variable
A workspace-level key-value store in Windmill for storing configuration or secrets. Variables can be plain text or secret (encrypted). They are accessible from scripts via environment variable injection.
Schedule
A cron-based or interval-based trigger in Windmill that automatically runs a script or flow on a defined schedule. Supports full cron expressions and timezone configuration.
Worker
A Windmill process that picks up and executes jobs from the queue. Workers can be specialized by worker group tags to run specific types of jobs.
Trigger
A mechanism in Windmill that initiates job execution based on external events. Supports HTTP webhooks, Postgres triggers, Kafka, SQS, MQTT, NATS, GCP Pub/Sub, Azure Service Bus, WebSocket, email, and native triggers.
App
A visual internal tool built on Windmill using a drag-and-drop UI builder. Apps interact with scripts and flows as backends. Equivalent to Retool or internal dashboards.
Path
A hierarchical identifier for scripts, flows, apps, resources, and variables in Windmill, using slash-separated segments with a user or folder prefix (e.g., u/username/my_script or f/folder/my_flow).
operationId
A unique camelCase identifier for each API operation in the Windmill OpenAPI spec, used by client SDKs and integration tooling to reference specific endpoints.
Git Sync
A Windmill feature that synchronizes workspace scripts, flows, and apps with a connected Git repository, enabling version control and GitOps workflows.
MCP
Model Context Protocol support in Windmill, enabling AI agents to discover and invoke Windmill scripts and flows as tools via the MCP standard.
Deno
A TypeScript/JavaScript runtime supported by Windmill scripts. Deno is the primary runtime for TypeScript scripts in Windmill, offering secure defaults and built-in TypeScript support.
Bun
A fast JavaScript/TypeScript runtime supported by Windmill as an alternative to Deno for running TypeScript scripts with improved performance.