ActionGitHubUpdated June 2026

How do I fetch a GitHub issue by number?

Short answer: Drop the "GitHub → Get Issue" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 23 GitHub actions

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.
Issue Number issue_number	string	Required	GitHub issue number — the integer shown after # in the issue URL (per-repo, not global).

Sample request

{
  "owner": "e.g. acme-corp",
  "repo": "e.g. my-project",
  "issue_number": "e.g. 42"
}

Returns

{
  "body": "Steps to reproduce...",
  "state": "open",
  "title": "Bug: Login crashes",
  "labels": [
    {
      "name": "bug"
    }
  ],
  "number": 42,
  "html_url": "https://github.com/acme-corp/my-project/issues/42",
  "assignees": [
    {
      "login": "johndoe"
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for Get Issue.

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 Get Issue.

What does the Get Issue action do in GitHub?

Retrieves a GitHub issue by its number with title, body, state, labels, assignees, and milestone. The standard read after a trigger fires with an issue number.

What inputs does Get Issue require?

Required: Repository Owner, Repository Name, Issue Number. 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 Issue support batch operations?

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