- Integrations
- /
- GitHub
- /
- Actions
- /
- List Issues
ActionGitHubUpdated May 2026
How do I list GitHub issues with filters?
Short answer: Drop the "GitHub → List Issues" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
|---|---|---|---|
Repository Owner owner | string | Required | GitHub repository owner — the user or organization login (the part before / in owner/repo URLs). |
Repository Name repo | string | Required | GitHub repository name — the part after / in owner/repo URLs. Not the full URL. |
State state | options | Optional | State. Options: Open, Closed, All |
Labels labels | string | Optional | Comma-separated label names to filter by |
Assignee assignee | string | Optional | Filter by assignee username. Use '*' for any, 'none' for unassigned. |
Sort By sort | options | Optional | Sort By. Options: Created, Updated, Comments |
Per Page per_page | string | Optional | Results per page (max 100) |
Sample request
{"owner": "e.g. acme-corp","repo": "e.g. my-project","state": "{{trigger.state}}","labels": "e.g. bug, high-priority","assignee": "e.g. johndoe"}
Returns
[{"state": "open","title": "Bug: Login crashes","labels": [{"name": "bug"}],"number": 42,"html_url": "https://github.com/acme-corp/my-project/issues/42"}]
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Issues.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Issues.
What does the List Issues action do in GitHub?
Lists issues in a GitHub repository with filters for state, assignee, labels, milestone, and update time. Used for triage reports or warehouse export.
What inputs does List Issues require?
Required: Repository Owner, Repository Name. 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 Issues support batch operations?
Yes. Run List Issues inside a Loop node to process arrays. Tiny Command handles GitHub's rate limits automatically so you don't have to throttle manually.
More actions
Other GitHub actions.
Action
Add Labels
Adds labels to a GitHub issue or pull request by name. Used for AI-driven triage or auto-tagging based on file paths touched.
ActionCreate Comment
Adds a comment to a GitHub issue or pull request. Used for AI review summaries, build-status pings, or status broadcasts from CI/CD.
ActionCreate Issue
Creates a new issue in a GitHub repository with title, body, assignees, labels, milestone, and project. The default write for piping bug reports or alerts into GitHub.
ActionCreate Pull Request
Creates a new pull request in a GitHub repository from a head branch to a base branch with title, body, and draft flag. Used for auto-PRs from generated code or dependency updates.
ActionSubmit PR Review
Submits a review on a GitHub pull request: APPROVE, REQUEST_CHANGES, or COMMENT. Used for AI code review or for cross-system approval gating.
ActionCreate Release
Creates a new release for a repository with tag name, target commitish, name, body (release notes), draft, and prerelease flags. Used to automate releases from your CI pipeline.
Send list issues from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.