Add Issue Comment
github.add_issue_comment
ActionBusiness appsconnection required
Calls the GitHub API POST /repos/{owner}/{repo}/issues/{n}/comments.
Comment on a GitHub issue or pull request.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- GitHub
- Secret shape
- the GitHub access token
- Resolved by
- config.connection_id, else node.connection_id, else the tenant's sole GitHub connection
Configuration
4 fields, 4 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
owner Repo owner. Supports {{ }}. | string | Yes | — | — | octocat |
repo Name of the repo to act on, from github.list_repos. | string | Yes | — | — | hello-world |
issue_number Issue or PR number. | string | Yes | — | — | 1 |
body Comment text. | string | Yes | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"issue_number": "1",
"owner": "octocat",
"repo": "hello-world"
}Output
One shape.
comment
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
comment_id | string | — |
html_url | string | — |
{
"comment_id": "",
"html_url": "",
"ok": false
}Solutions with GitHub
See Add Issue Comment run in a workflow.
In a technical demo we add the GitHub connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.