List Workflows

github.list_workflows
ActionBusiness appsconnection required

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

List the GitHub Actions workflows defined in a repository.

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, 2 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
max_items
Stop after this many rows; further pages are followed via the Link header.
numberNo1001–1000—

Example configuration

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

{
  "max_items": 100,
  "owner": "octocat",
  "repo": "hello-world"
}

Output

One shape.

result

FieldTypeExample
workflows
The workflows this step read.
array—
workflows[].id
Workflow id, accepted anywhere workflow_id is asked for.
number—
workflows[].name
Workflow name from its YAML.
string—
workflows[].path
Path of the workflow file.
string—
workflows[].state
active, disabled_manually, disabled_inactivity…
string—
workflows[].html_url
Link to the workflow.
string—
count
How many rows this step returned.
number—
{
  "count": 0,
  "workflows": [
    {
      "html_url": "",
      "id": 0,
      "name": "",
      "path": "",
      "state": ""
    }
  ]
}

See List Workflows 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.