ActionGitHubUpdated June 2026

How do I list GitHub Actions workflow runs?

Short answer: You can list workflow runs in GitHub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitHub List Workflow Runs action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Workflow Runs in GitHub — start free All 23 GitHub actions

List Workflow Runs in GitHub — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Owner owner	string	Required	GitHub repository owner — the user or organization login (the part before / in owner/repo URLs).
Repository repo	string	Required	GitHub repository name — the part after / in owner/repo URLs. Not the full URL.
Status Filter status	options	Optional	Status Filter. Options: All, Completed, In Progress, Queued, Failed, Success
Results Per Page per_page	number	Optional	Results Per Page

Sample request

{
  "owner": "e.g. octocat",
  "repo": "e.g. hello-world",
  "status": "{{trigger.status}}",
  "per_page": "{{trigger.per_page}}"
}

Returns

{
  "total_count": 3,
  "workflow_runs": [
    {
      "id": 1,
      "name": "CI",
      "status": "completed",
      "conclusion": "success"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Workflow Runs.

Any of these apps can fire this action as part of a workflow.

Google Sheets → GitHub

2 Google Sheets triggers

HubSpot → GitHub

18 HubSpot triggers

FAQ

Questions about List Workflow Runs.

What does the List Workflow Runs action do in GitHub?

Lists workflow runs for a repository with status, conclusion, branch, and timing. Used for CI dashboards and for triggering downstream automation when a build completes.

What inputs does List Workflow Runs require?

Required: Owner, Repository. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if GitHub returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Workflow Runs support batch operations?

Yes. Run List Workflow Runs inside a Loop node to process arrays. TinyCommand handles GitHub's rate limits automatically so you don't have to throttle manually.

More actions