Add Issue Labels
github.add_issue_labels
ActionBusiness appsconnection required
Calls POST /repos/{owner}/{repo}/issues/{issue_number}/labels.
Add labels to an issue without disturbing the ones already on it.
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
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 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 |
labels Label names, as a JSON array or a comma-separated list. | array | Yes | — | array of string | ["bug"] |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"issue_number": "1",
"labels": [
"bug"
],
"owner": "octocat",
"repo": "hello-world"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when GitHub accepted the call. | boolean | true |
labels Label names on the issue after the change. | array | — |
count How many labels the issue now has. | number | — |
{
"count": 0,
"labels": [],
"ok": true
}Notes
- A label that does not exist in the repository is created by this call.
Solutions with GitHub
See Add Issue Labels 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.