ActionGitHubUpdated September 2026

How do I fetch a GitHub pull request?

Short answer: You can get pull request in GitHub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitHub Get Pull Request action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Pull Request in GitHub — start free All 23 GitHub actions

Get Pull Request 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
Owner owner	string	Required	GitHub repository owner — the user or organization login (the part before / in owner/repo URLs).
Repository repo	string	Required	GitHub repository name — the part after / in owner/repo URLs. Not the full URL.
PR Number pull_number	number	Required	GitHub pull request number — the integer shown after /pull/ in the PR URL (per-repo, not global).

Sample request

{
  "owner": "e.g. octocat",
  "repo": "e.g. hello-world",
  "pull_number": "e.g. 137"
}

Returns

{
  "id": 1,
  "base": {
    "ref": "main"
  },
  "body": "Fixes the login issue",
  "head": {
    "ref": "feature/fix-login"
  },
  "state": "open",
  "title": "Fix login bug",
  "merged": false,
  "number": 42
}

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

Triggered by

Apps that pair well as the trigger for Get Pull Request.

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 Pull Request.

What does the Get Pull Request action do in GitHub?

Gets details of a GitHub pull request: title, body, state, head/base, mergeable, reviewers, labels, and diff stats. Used to enrich a PR-event trigger.

What inputs does Get Pull Request require?

Required: Owner, Repository, PR 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 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 Get Pull Request support batch operations?

Run Get Pull Request 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