ActionGitHubUpdated September 2026

How do I fetch a GitHub repository's details?

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

Get Repository in GitHub — start free All 23 GitHub actions

Get Repository 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
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.

Sample request

{
  "owner": "e.g. acme-corp",
  "repo": "e.g. my-project"
}

Returns

{
  "id": 123456,
  "private": true,
  "html_url": "https://github.com/acme-corp/my-project",
  "language": "TypeScript",
  "full_name": "acme-corp/my-project",
  "description": "Our main project repo",
  "forks_count": 5,
  "default_branch": "main",
  "stargazers_count": 42,
  "open_issues_count": 12
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Repository.

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 Get Repository.

What does the Get Repository action do in GitHub?

Retrieves details of a GitHub repository: name, description, default branch, visibility, license, topics, and stats. Used to enrich a trigger or render repo info.

What inputs does Get Repository 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 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 Get Repository support batch operations?

Run Get Repository 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