Get Repository: GitHub action

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.

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

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