ActionGitHubUpdated September 2026

How do I list GitHub repositories for a user or org?

Short answer: You can list repositories in GitHub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitHub List Repositories action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Repositories in GitHub — start free All 23 GitHub actions

List Repositories in GitHub — start free

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.

Google Sheets → GitHub

2 Google Sheets triggers

HubSpot → GitHub

18 HubSpot triggers

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 run history shows the failed step with its input and the error message GitHub returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Repositories support batch operations?

Run List Repositories inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within GitHub's rate limits.

More actions