ActionGitHubUpdated September 2026

How do I search GitHub issues and PRs across repos?

Short answer: You can search issues in GitHub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitHub Search Issues 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 Issues in GitHub — start free All 23 GitHub actions

Search Issues 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 issues by title, body, or labels. Supports GitHub search syntax.
Limit limit	number	Optional	Maximum results (max 50)

Sample request

{
  "query": "e.g. is:open label:bug repo:owner/repo",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "items": [
    {
      "id": 456,
      "state": "open",
      "title": "Bug: login fails",
      "number": 42,
      "html_url": "https://github.com/owner/repo/issues/42"
    }
  ],
  "total_count": 25
}

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

Triggered by

Apps that pair well as the trigger for Search Issues.

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 Issues.

What does the Search Issues action do in GitHub?

Searches GitHub issues and pull requests across repositories using GitHub's search syntax (repo:, author:, label:, state:). Heavily rate-limited; cache results aggressively.

What inputs does Search Issues 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 Issues support batch operations?

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