Search Repositories: 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
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.

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 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 Search Repositories support batch operations?

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