Argo Workflow Template Builder
Build Argo WorkflowTemplate and ClusterWorkflowTemplate YAML visually. Free, no sign-up, and everything runs privately in your browser.
How to use the template builder
- Choose WorkflowTemplate (namespaced) or ClusterWorkflowTemplate (cluster-wide).
- Add, edit or remove templates. Use
{{inputs.parameters.NAME}}in commands and list NAME under input parameters. - Pick an orchestration mode: sequential steps, a DAG (fill in “Depends on”), or a library with no entrypoint.
- Check the live structure status, then copy or download the YAML.
Template settings
Templates
Generated YAML
Apply and submit
WorkflowTemplate or ClusterWorkflowTemplate?
A WorkflowTemplate lives in one namespace and is ideal for a team’s own pipelines. A ClusterWorkflowTemplate has no namespace and can be referenced from any namespace with templateRef and clusterScope: true, which makes it the right choice for organisation-wide building blocks such as notifications or image scanning. The builder hides the namespace field automatically when you pick the cluster-scoped kind.
How the builder wires your templates
In DAG mode the builder creates a main template whose tasks call each of your templates; the “Depends on” field is copied into the task’s depends expression, so you can use plain names or selectors such as build.Succeeded. In Sequential steps mode each template becomes its own stage. In Library mode no entrypoint is created — the templates are meant to be borrowed individually with templateRef. Any input parameter you list is exposed as a workflow argument and passed through automatically.
Live structure checking
As you edit, the builder runs the same checks as our validator: undefined dependencies, cycles, missing images and undeclared parameters are reported immediately under the output, so the template you download is structurally valid.
Frequently asked questions
How do I submit the template after applying it?
Use argo submit --from workflowtemplate/NAME -p param=value. The builder prints the exact command for your template.
Can I version templates?
Yes — include a version in the name (for example build-image-v2) for widely shared templates, as explained in our templates guide.
Why do script templates use Python?
Python is the most common choice for inline scripts. Change the image and command in the YAML if you need another language.
More free tools
YAML Generator
Build a complete Workflow or WorkflowTemplate manifest from a simple form.
CronWorkflow Generator
Generate CronWorkflows with schedules, timezones and next-run previews.
DAG Visualizer
Paste YAML and see your DAG or steps rendered as a graph.
YAML Validator
Catch syntax and structural errors before you submit to the cluster.