How to search issues in GitHub

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.

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

Yes. Run Search Issues inside a Loop node to process arrays. TinyCommand handles GitHub's rate limits automatically so you don't have to throttle manually.

More actions