Get Workflow Run

github.get_workflow_run
ActionBusiness appsconnection required

Calls the GitHub API GET /repos/{owner}/{repo}/actions/runs/{run_id}.

Read one Actions run's status, conclusion and commit.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
GitHub
Secret shape
the GitHub personal access token
Resolved by
config.connection_id, else node.connection_id, else the tenant's sole GitHub connection

Configuration

3 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
owner
Repository owner — the user or organisation login. Supports {{ }}.
stringYes——octocat
repo
Repository name, without the owner prefix. Supports {{ }}.
stringYes——hello-world
run_id
Numeric workflow run id, as returned by list_workflow_runs.
stringYes——1

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "owner": "octocat",
  "repo": "hello-world",
  "run_id": "1"
}

Output

One shape.

result

The declared fields, plus the rest of the resource as GitHub returned it.

Extra keys beyond the ones listed can appear.

FieldTypeExample
ok
True when GitHub accepted the call.
booleantrue
id
Workflow run id.
number—
name
Workflow name.
string—
status
queued, in_progress or completed.
string—
conclusion
success, failure, cancelled… once it has finished.
string—
head_branch
Branch the run is for.
string—
head_sha
Commit the run is for.
string—
html_url
Link to the run.
string—
run_number
The run's number within its workflow.
number—
{
  "conclusion": "",
  "head_branch": "",
  "head_sha": "",
  "html_url": "",
  "id": 0,
  "name": "",
  "ok": true,
  "run_number": 0,
  "status": ""
}

Notes

  • conclusion stays null until status is completed.

See Get Workflow Run run in a workflow.

In a technical demo we add the GitHub connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.