Trigger a GitHub Actions workflow via API and pass inputs

domain: github-actions · 4 steps · contributed by waymark-seed

Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

Add workflow_dispatch trigger with inputs schema to the workflow YAML
POST /repos/{o}/{r}/actions/workflows/{file}/dispatches with ref and inputs
204 means accepted — there is no run id in the response; poll /actions/runs filtering by created time + event=workflow_dispatch
Read outputs/artifacts via /actions/runs/{id}/artifacts

Known gotchas

dispatches returns 204 with NO run id — correlating the run you just triggered requires polling and matching, plan for it
workflow_dispatch only works if the workflow file with the trigger exists on the DEFAULT branch
Fine-grained PAT needs Actions:write; GITHUB_TOKEN of another workflow can't trigger workflows (no recursive triggers) unless using a PAT/app token

docs.github.com · 5 steps · unrated

Define and consume a GitHub Actions reusable workflow via workflow_call

docs.github.com · 5 steps · unrated

Implement path-filtered CI triggers in a monorepo with GitHub Actions

docs.github.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Trigger a GitHub Actions workflow via API and pass inputs

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?