List Issues
github.list_issues
ActionBusiness appsconnection required
Calls the GitHub API GET /repos/{owner}/{repo}/issues.
List issues in a GitHub repository.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- GitHub
- Secret shape
- the GitHub access token
- Resolved by
- config.connection_id, else node.connection_id, else the tenant's sole GitHub connection
Configuration
5 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
owner Repo owner. Supports {{ }}. | string | Yes | — | — | octocat |
repo Name of the repo to act on, from github.list_repos. | string | Yes | — | — | hello-world |
state open | closed | all. | string | No | open | one of "open", "closed", "all" | — |
labels Comma-separated label filter. | string | No | — | — | — |
per_page Max issues (1-100). | number | No | 30 | ≥ 1 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"owner": "octocat",
"per_page": 30,
"repo": "hello-world",
"state": "open"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
issues | array | — |
count | number | — |
{
"count": 0,
"issues": []
}Solutions with GitHub
See List Issues 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.