Short answer: Drop the "GitHub → Submit PR Review" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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). |
Review Action event | options | Required | Review Action. Options: Approve, Request Changes, Comment |
Review Comment body | string | Optional | Message body content. Plain text unless the API specifies HTML/markdown. |
{"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."}
{"id": 80,"body": "LGTM!","user": {"login": "octocat"},"state": "APPROVED"}
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.
Triggered by anything in the catalog. Free tier available. No credit card.