ActionGitHubUpdated June 2026

How do I submit a review on a GitHub PR?

Short answer: Drop the "GitHubSubmit PR Review" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Owner
owner
stringRequiredGitHub repository owner — the user or organization login (the part before / in owner/repo URLs).
Repository
repo
stringRequiredGitHub repository name — the part after / in owner/repo URLs. Not the full URL.
PR Number
pull_number
numberRequiredGitHub pull request number — the integer shown after /pull/ in the PR URL (per-repo, not global).
Review Action
event
optionsRequiredReview Action. Options: Approve, Request Changes, Comment
Review Comment
body
stringOptionalMessage body content. Plain text unless the API specifies HTML/markdown.
Sample request
{
"owner": "e.g. octocat",
"repo": "e.g. hello-world",
"pull_number": "e.g. 137",
"event": "{{trigger.event}}",
"body": "e.g. Hi there, thanks for reaching out."
}
Returns
{
"id": 80,
"body": "LGTM!",
"user": {
"login": "octocat"
},
"state": "APPROVED"
}

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

Triggered by

Apps that pair well as the trigger for Submit PR Review.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Submit PR Review.

What does the Submit PR Review action do in GitHub?
Submits a review on a GitHub pull request: APPROVE, REQUEST_CHANGES, or COMMENT. Used for AI code review or for cross-system approval gating.
What inputs does Submit PR Review require?
Required: Owner, Repository, PR Number, Review Action. 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 Submit PR Review support batch operations?
Yes. Run Submit PR Review 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

Other GitHub actions.

Action
Add Labels
Adds labels to a GitHub issue or pull request by name. Used for AI-driven triage or auto-tagging based on file paths touched.
Action
Create Comment
Adds a comment to a GitHub issue or pull request. Used for AI review summaries, build-status pings, or status broadcasts from CI/CD.
Action
Create Issue
Creates a new issue in a GitHub repository with title, body, assignees, labels, milestone, and project. The default write for piping bug reports or alerts into GitHub.
Action
Create or Update File
Creates or updates a file in a GitHub repository in a single commit, with branch, commit message, and content. The SHA is auto-fetched on update; the standard tool for small file commits without a full git client.
Action
Create Pull Request
Creates a new pull request in a GitHub repository from a head branch to a base branch with title, body, and draft flag. Used for auto-PRs from generated code or dependency updates.
Action
Create Release
Creates a new release for a repository with tag name, target commitish, name, body (release notes), draft, and prerelease flags. Used to automate releases from your CI pipeline.

Send submit pr review from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.