ActionGitHubUpdated September 2026

How do I search GitHub repositories?

Short answer: You can search repositories in GitHub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitHub Search Repositories 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.

Search Repositories in GitHub — start free All 23 GitHub actions

Search 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
Search Query query	string	Required	Search repositories by name, description, or topic
Limit limit	number	Optional	Maximum results (max 50)

Sample request

{
  "query": "{{trigger.query}}",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "items": [
    {
      "id": 123,
      "html_url": "https://github.com/owner/repo",
      "full_name": "owner/repo",
      "description": "A cool project"
    }
  ],
  "total_count": 50
}

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

Triggered by

Apps that pair well as the trigger for Search 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 Search Repositories.

What does the Search Repositories action do in GitHub?

Searches GitHub repositories by name, topic, language, or stars using GitHub's search syntax. Heavily rate-limited (10 req/min for unauthenticated; 30 for authenticated).

What inputs does Search Repositories require?

Required: Search Query. 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 Search Repositories support batch operations?

Run Search 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