write-flow

Creating a Windmill flow involves defining a YAML file that adheres to the OpenFlow schema, specifying module IDs, script references, and subflows. Structure your flow with unique module identifiers, reference inline rawscript or path-based scripts, then deploy using the Windmill CLI to generate locks and push to your environment.

The OpenFlow schema is the structured specification that Windmill flows must follow to execute correctly. Adhering to it ensures your flow definitions are valid, prevents module ID conflicts, and enables proper routing of data through sequences of steps, tests, and deployments.

Common pitfalls include duplicate module IDs, incorrect script path references, and schema violations. This Skill documents best practices for flow design, module naming, and error handling to reduce manual drafting errors and deployment issues before they reach production.

Yes. Windmill flows support both inline rawscript and path-based script references, as well as subflows. You can mix these approaches within a single flow definition to compose modular workflows that process events, apply tests, and route to deployments.

Create a flow folder with a YAML file conforming to OpenFlow schema, reference your scripts or subflows, run the Windmill CLI to generate locks, then deploy. This ensures consistent configuration and error handling rules are applied as your flow moves across dev, test, and production environments.

While manual authoring is possible, using ready-to-use templates reduces setup time and drafting errors. Templates provide scaffolding aligned with OpenFlow schema conventions, module ID patterns, and best practices for defining multi-step workflows and error handlers.