ActionGitHubUpdated May 2026

How do I list GitHub pull requests?

Short answer: Drop the "GitHub → List Pull Requests" 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.
State state	options	Optional	State. Options: Open, Closed, All
Sort sort	options	Optional	Sort. Options: Created, Updated, Popularity
Per Page per_page	string	Optional	Per Page. e.g. "30"

Sample request

{
  "owner": "e.g. acme-corp",
  "repo": "e.g. my-project",
  "state": "{{trigger.state}}",
  "sort": "{{trigger.sort}}",
  "per_page": "30"
}

Returns

[
  {
    "user": {
      "login": "johndoe"
    },
    "state": "open",
    "title": "Fix login",
    "number": 99,
    "html_url": "https://github.com/acme/my-project/pull/99"
  }
]

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

Triggered by

Apps that pair well as the trigger for List Pull Requests.

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 List Pull Requests.

What does the List Pull Requests action do in GitHub?

Lists pull requests in a repository with filters for state (open/closed/all), head, base, and sort. Used for review-queue dashboards and stale-PR cleanup.

What inputs does List Pull Requests require?

Required: Repository Owner, Repository Name. 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 List Pull Requests support batch operations?

Yes. Run List Pull Requests 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