;}%20.st6{fill:url(%23SVGID_00000021089067129159788970000008246765442136188072_);}%20.st7{fill:url(%23SVGID_00000117639240116366130650000015074833605515028638_);}%20.st8{opacity:0.4;fill:url(%23SVGID_00000101781798616409025840000016567063639337360777_);}%20.st9{opacity:0.4;fill:url(%23SVGID_00000052086836598721292040000002033117744178971046_);}%20.st10{opacity:0.4;fill:url(%23SVGID_00000159460939004760751800000002448009281983951536_);}%20.st11{opacity:0.4;fill:url(%23SVGID_00000013177830667419993080000017721442101626521532_);}%20.st12{opacity:0.4;fill:url(%23SVGID_00000152235521444854938490000006526001119318383285_);}%20.st13{opacity:0.4;fill:url(%23SVGID_00000119823135212293698520000012774889010992664993_);}%20%3c/style%3e%3cg%3e%3cpolygon%20class='st2'%20points='134.78,14.22%20114.31,48.21%20101.33,69.75%20158.22,69.75%20177.97,36.95%20191.67,14.22%20'/%3e%3cpolygon%20class='st3'%20points='227.55,69.75%20186.61,69.75%20101.33,69.75%20129.78,119.02%20158.16,119.02%20228.61,119.02%20256,119.02%20'/%3e%3cpolygon%20class='st3'%20points='136.93,132.47%20116.46,167.93%2073.82,241.78%20130.71,241.78%20144.9,217.2%20180.13,156.18%20193.82,132.46%20'/%3e%3cpolygon%20class='st3'%20points='121.7,131.95%20101.23,96.49%2058.59,22.63%2030.15,71.91%2044.34,96.49%2079.57,157.5%2093.26,181.22%20'/%3e%3cpolygon%20class='st2'%20points='64.81,131.95%2025.15,131.21%200,130.74%2028.44,180.01%2066.73,180.72%2093.26,181.21%20'/%3e%3cpolygon%20class='st2'%20points='165.38,181.74%20184.58,216.46%20196.75,238.47%20225.19,189.2%20206.66,155.69%20193.83,132.46%20'/%3e%3c/g%3e%3c/svg%3e)
Windmill HubOpen issues, review and merge pull requests, commit files and dispatch Actions workflows from any Windmill script, flow or app.
What you can do with GitHub
Complete, deployable projects built around GitHub — the fastest way to get something real running.
Github release dashboard
Browse a repo's latest releases
Support automation
AI support triage with a human approval gate: classify, analyze, draft the reply, dispatch clear-cut fixes in parallel.
Github release digest
Browse a repo's latest releases
Content engine
Content engine
Support engine
Drafts replies to your support inbox into Gmail drafts, ready for you to send.
Sales engine
Finds leads matching your ICP, drafts an email to the ones worth writing to, and leaves them in Gmail drafts.
Sentry engine
Investigates recurring production errors and opens a pull request with the diagnosis, and the fix when it is sure.
Newsletter engine
Draft a newsletter on Resend based on recent changelogs
Set up in 2 steps
Connect from the Resources page
Open Resources, click Add a resource/API and pick github from the OAuth APIs list. Click Connect, allow access in the window that opens, then name the resource and save it. Windmill asks GitHub for the repo and workflow scopes; tick gist for the gist scripts, read:project or project for the Projects scripts, or read:org to see private organization memberships.
Run your first script
Fork any script below and run it against one of your repositories.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
Update Pull Request
Update Project Item Status
Update Issue
Update Gist
Sync Fork Branch with Upstream
Star Repository
Search Issues and Pull Requests
Re-run Failed Jobs
Merge Pull Request
List Workflows
List Workflow Runs
List Repository Labels
List Repository Collaborators
List Repositories
List Releases
List Pull Requests
List Projects
List Project Statuses
List Project Items
List Organizations
List Organization Repositories
List Milestones
List Issues
List Issue Comments
List Gists
List Commits
List Branches
Get Workflow Run
Get Reviewers
Get Repository Content
Flows
Multi-step workflows that already wire GitHub to something else.
Trigger flows from GitHub
GitHub is not only a destination. These inbound paths are supported today.
GitHub events (native GitHub trigger)
Connect GitHub once under Workspace settings > Integrations, then add a GitHub trigger on a script or flow, pick a repository and the events to listen to (push, pull_request, issues, release, star, workflow_run and more). Windmill creates the repository webhook for you, which needs admin rights on the repository, and starts a run with the event name and payload on every delivery. Fork the GitHub native trigger template script to get started.
Webhooks you manage yourself
To use a webhook you configured by hand (an organization webhook, say), point it at a flow's webhook URL and verify the X-Hub-Signature-256 header against your webhook secret.
Resource types
The credential shapes the scripts on this page expect — pick the one your script asks for.
github
View raw schema →| Field | Type | Required | What it is |
|---|---|---|---|
| token | string | Yes |
github_app
View raw schema →| Field | Type | Required | What it is |
|---|---|---|---|
| app_id | string | Yes | |
| private_key | string | Yes | |
| installation_id | string | No |
Questions
OAuth or a personal access token?
OAuth is one click and the token it stores does not expire. Reach for a personal access token when you script the setup, when you want a token scoped to fewer repositories, or when your instance has no OAuth client configured.
Classic or fine-grained token?
Either works. Fine-grained tokens are scoped per repository and expire.
There is no Connect button on my instance
Self-hosted instances need an OAuth client configured once by an admin before the tile appears. Until then, use the token.