Short answer: Drop the "GitHub → Create Comment" 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 |
|---|---|---|---|
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. |
Issue or PR Number issue_number | string | Required | GitHub issue number — the integer shown after # in the issue URL (per-repo, not global). |
Comment Body body | string | Required | Comment text (supports GitHub Markdown) |
{"owner": "e.g. acme-corp","repo": "e.g. my-project","issue_number": "e.g. 42","body": "e.g. Looks like this is related to #38. Investigating..."}
{"id": 1,"body": "Looks like this is related to #38.","user": {"login": "johndoe"},"html_url": "https://github.com/acme-corp/my-project/issues/42#issuecomment-1","created_at": "2025-01-15T12:00:00Z"}
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.