Visual GitHub Actions workflow generator
Design a workflow with events, jobs and steps in your browser, check for errors and security risks, and generate the YAML file for .github/workflows/. You can also import a .yml file you already have.
What you can do
- Design workflows visually with jobs and dependencies.
- Configure events, jobs and steps.
- Import existing YAML files within the supported scope.
- Use Python, Node.js and Docker templates.
- Validate structure and logic, and detect certain security risks.
- Generate YAML files for .github/workflows/.
- Save projects.
How it works
- DesignStart from a template or from scratch: choose the events, add jobs and steps and connect the dependencies (needs).
- ValidateReview errors, warnings and security risks before generating the file.
- GenerateDownload or copy the YAML and save it in .github/workflows/ in your repository.
Templates with the real YAML
Three starting points with the exact file the application generates, ready to copy:
- Python: testsInstalls dependencies and runs pytest on several Python versions with pip caching.
- Node.js: lint, tests and buildInstalls with npm ci and runs lint, tests and build on several Node versions with npm caching.
- Docker: build and publish to GHCRBuilds the repository image and publishes it to GitHub Container Registry (ghcr.io) when you push to main or create a v* tag.
What the validator checks
- Structure: jobs without steps, invalid identifiers, and needs dependencies that are missing, point to themselves or form a cycle.
- ${{ }} expressions: syntax, and contexts and functions that do not exist at that point.
- Events: filters that conflict with each other and invalid cron schedules.
- Matrices: empty dimensions or too many combinations.
- Logic: a job that would never run because its if condition excludes the one of the job it depends on.
- Security: unpinned actions and Docker images, missing or write-all permissions, credentials or secrets written in clear text and possible command injection.
What it does not do
- It does not run your workflows or connect to your GitHub repository: you upload the file yourself.
- It does not replace GitHub: the validator is an aid, and GitHub Actions has the final say when it runs.
- When importing, the YAML is analyzed as data and is never executed.
Frequently asked questions
Where do I save the generated file?
In the .github/workflows/ folder of your repository (for example .github/workflows/ci.yml). GitHub detects it when you push it and runs it according to the events you defined.
Can I import a workflow I already have?
Yes, within the supported scope. The file is read as data; keys the tool does not know are rejected with a message that points to the line, instead of being silently lost.
Do the templates really work?
The three templates (Python, Node.js and Docker) were generated from the application and ran green in a real GitHub repository. They are still a starting point: adapt them to your project.
What does the validator check about security?
Among other things, it warns about third-party actions not pinned to a commit, missing permissions, secrets written in clear text and expression uses that could allow command injection. These are guidance warnings, not an audit.
Does it cost anything?
No. It is free, with usage limits (new projects per day, exports per month and saved projects) that you will always see inside your account.
Also available
- Apache AirflowDesign Airflow 3 DAGs and generate the Python file.
Try it for free
The editor is available with a free account, with usage limits. Nothing runs in your repository or your installation: you decide which file to use.