Close Issue
github.close_issue
ActionBusiness appsconnection required
Calls PATCH /repos/{owner}/{repo}/issues/{issue_number} with state closed.
Close an issue, optionally recording why it was closed.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- GitHub
- Secret shape
- the GitHub personal access token
- Resolved by
- config.connection_id, else node.connection_id, else the tenant's sole GitHub connection
Configuration
5 fields, 3 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 Repository owner — the user or organisation login. Supports {{ }}. | string | Yes | — | — | octocat |
repo Repository name, without the owner prefix. Supports {{ }}. | string | Yes | — | — | hello-world |
issue_number Issue number as shown in the UI (not the internal id). | string | Yes | — | — | 1 |
state_reason Why it was closed; GitHub shows completed and not_planned differently. | string | No | completed | one of "completed", "not_planned", "duplicate" | — |
duplicate_issue_id Internal id of the issue this one duplicates. GitHub requires it when state_reason is duplicate, and ignores it otherwise. | string | Conditional | — | only with state_reason | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"issue_number": "1",
"owner": "octocat",
"repo": "hello-world",
"state_reason": "completed"
}Output
One shape.
result
The declared fields, plus the rest of the resource as GitHub returned it.
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
ok True when GitHub accepted the call. | boolean | true |
number Issue number as shown in the UI. | number | — |
title Issue title. | string | — |
state open or closed. | string | — |
state_reason Why it is in that state, when GitHub recorded one. | string | — |
body Issue body (Markdown). | string | — |
html_url Link to the issue. | string | — |
comments How many comments it has. | number | — |
{
"body": "",
"comments": 0,
"html_url": "",
"number": 0,
"ok": true,
"state": "",
"state_reason": "",
"title": ""
}Notes
- GitHub has no delete-an-issue endpoint; closing is as far as the API goes.
- state_reason 'duplicate' also needs duplicate_issue_id, or GitHub answers 422.
Solutions with GitHub
See Close Issue 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.