ActionGitHubUpdated September 2026

How do I add labels to a GitHub issue or PR?

Short answer: You can add labels in GitHub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitHub Add Labels action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Add Labels in GitHub — start free All 23 GitHub actions

Add Labels in GitHub — start free

Inputs

The fields this action accepts.

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.
Issue / PR Number issue_number	number	Required	GitHub issue number — the integer shown after # in the issue URL (per-repo, not global).
Labels labels	array	Required	Array of label names to apply to the issue. Each item must match an existing label on the repo exactly (case-sensitive). New labels are not auto-created.

Sample request

{
  "owner": "e.g. octocat",
  "repo": "e.g. hello-world",
  "issue_number": "e.g. 42",
  "labels": "[\"bug\", \"help wanted\"]"
}

Returns

[
  {
    "id": 1,
    "name": "bug",
    "color": "d73a4a"
  }
]

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Add Labels.

Any of these apps can fire this action as part of a workflow.

Google Sheets → GitHub

2 Google Sheets triggers

HubSpot → GitHub

18 HubSpot triggers

FAQ

Questions about Add Labels.

What does the Add Labels action do in GitHub?

Adds labels to a GitHub issue or pull request by name. Used for AI-driven triage or auto-tagging based on file paths touched.

What inputs does Add Labels require?

Required: Owner, Repository, Issue / PR Number, Labels. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if GitHub returns an error?

The run history shows the failed step with its input and the error message GitHub returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Add Labels support batch operations?

Run Add Labels inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within GitHub's rate limits.

More actions