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.
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). |
{"owner": "e.g. octocat","repo": "e.g. hello-world","pull_number": "e.g. 137"}
{"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.
Any of these apps can fire this action as part of a workflow.