- Integrations
- /
- GitHub
- /
- Actions
- /
- List Repositories
ActionGitHubUpdated May 2026
How do I list GitHub repositories for a user or org?
Short answer: Drop the "GitHub → List Repositories" 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 |
|---|---|---|---|
Type type | options | Optional | Type. Options: Owner, All (including collabs), Member |
Sort sort | options | Optional | Sort. Options: Updated, Created, Full Name |
Per Page per_page | string | Optional | Per Page. e.g. "30" |
Sample request
{"type": "{{trigger.type}}","sort": "{{trigger.sort}}","per_page": "30"}
Returns
[{"private": true,"html_url": "https://github.com/acme/my-project","full_name": "acme/my-project","default_branch": "main"}]
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Repositories.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Repositories.
What does the List Repositories action do in GitHub?
Lists repositories for the authenticated user or a specific organization. Used to populate a repo picker before any cross-repo automation.
What inputs does List Repositories require?
List Repositories has no required inputs. Sensible defaults are applied if you leave fields blank.
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 Repositories support batch operations?
Yes. Run List Repositories 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 repositories from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.