How to use GitHub Actions Workflow Builder
Get the best out of GitHub Actions Workflow Builder: every option explained, a worked example, and what to check when the output is not what you expected.
Updated July 31, 2026
What it does
Compose starter CI workflow YAML for lint, test, and build pipelines. It runs entirely in your browser — your input never leaves your device.
Options
Every setting this tool exposes, straight from the code that validates it.
| Option | Type | Default | What it does |
|---|---|---|---|
workflowName | text | CI | Defaults to CI. |
runtime | one of: node, python | node | Defaults to node. |
runtimeVersion | text | 22 | Defaults to 22. |
packageManager | one of: npm, pnpm, yarn | npm | Defaults to npm. |
pushTrigger | true / false | true | Defaults to true. |
pullRequestTrigger | true / false | true | Defaults to true. |
manualTrigger | true / false | false | Defaults to false. |
installStep | true / false | true | Defaults to true. |
lintStep | true / false | true | Defaults to true. |
testStep | true / false | true | Defaults to true. |
buildStep | true / false | true | Defaults to true. |
Worked example
Run these settings on the tool page:
workflowName:CIruntime:noderuntimeVersion:22packageManager:npmpushTrigger:truepullRequestTrigger:truemanualTrigger:falseinstallStep:truelintStep:truetestStep:truebuildStep:true
You get:
name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
quality:
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Setup node
uses: actions/setup-node@v4
with:
node-version: 22
- name: Install dependencies
run: |
npm install
- name: Lint
run: |
npm run lint
- name: Test
run: |
npm test
- name: Build
run: |
npm run build
Getting the result you want
Most of the control here is in the options above. If the output is not what you expected, the setting to check first is workflowName and runtime — those change the shape of the output rather than the input it accepts.
Troubleshooting
- It is slow on very large input. Everything runs in your browser, so speed depends on your device. Very large inputs are best split up, or run through the API where the work happens on our servers.
Automating it
The same logic is available as a REST endpoint, so you can run it from a script, a CI job or your own app.
Bashcurl "https://api.toolsxpo.com/v1/github-actions-builder" \ -H "Authorization: Bearer $TOOLSXPO_KEY"
It costs 1 credit per successful call. See the full endpoint reference, or try it in the playground.
Related tools
Tools covered here
Related
How to use AES Encryption
Get the best out of AES Encryption: every option explained, a worked example, and what to check when the output is not what you expected.
How to use API Mock Payload Builder
Get the best out of API Mock Payload Builder: every option explained, a worked example, and what to check when the output is not what you expected.
How to use ASCII Chart
Get the best out of ASCII Chart: every option explained, a worked example, and what to check when the output is not what you expected.
How to use ASCII to Text
Get the best out of ASCII to Text: every option explained, a worked example, and what to check when the output is not what you expected.