ActionGitHubUpdated September 2026

How do I update a GitHub issue?

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

Update Issue in GitHub — start free All 23 GitHub actions

Update Issue 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
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 Number issue_number	string	Required	GitHub issue number — the integer shown after # in the issue URL (per-repo, not global).
Title title	string	Optional	Title
Body body	string	Optional	Message body content. Plain text unless the API specifies HTML/markdown.
State state	options	Optional	State. Options: Open, Closed
Labels labels	array	Optional	Array of label names to set on the issue. Note: this REPLACES the existing labels (it does not append). To preserve current labels, fetch them first and merge. Empty array clears all labels.
Assignees assignees	array	Optional	Array of GitHub usernames to set as assignees. REPLACES the existing assignees, not appends. Each user must have push access.

Sample request

{
  "owner": "e.g. acme-corp",
  "repo": "e.g. my-project",
  "issue_number": "e.g. 42",
  "title": "{{trigger.title}}",
  "body": "e.g. Hi there, thanks for reaching out."
}

Returns

{
  "state": "open",
  "title": "Updated title",
  "number": 42
}

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

Triggered by

Apps that pair well as the trigger for Update Issue.

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 Update Issue.

What does the Update Issue action do in GitHub?

Updates an existing GitHub issue: title, body, state, assignees, labels, or milestone. Only the fields you pass are changed.

What inputs does Update Issue require?

Required: Repository Owner, Repository Name, Issue Number. 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 Update Issue support batch operations?

Run Update Issue 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