List Issues
gitlab.list_issues
ActionBusiness appsconnection required
Calls the GitLab API GET /projects/{id}/issues.
List issues in a GitLab project.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- GitLab
- Secret shape
- the GitLab access token
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 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 |
|---|---|---|---|---|---|
project Project id or namespace/path. Supports {{ }}. | string | Yes | — | — | — |
state opened | closed | all. | string | No | opened | one of "opened", "closed", "all" | — |
per_page Max issues (1-100). | number | No | 20 | ≥ 1 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"per_page": 20,
"state": "opened"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
issues | array | — |
count | number | — |
{
"count": 0,
"issues": []
}Related GitLab nodes
Solutions with GitLab
See List Issues run in a workflow.
In a technical demo we add the GitLab connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.