Four GitHub steps work with issues in a repository. GitHub · Create an issue — Opens an issue in a repository. GitHub · Update an issue — Changes an issue's state, title, labels or assignees. GitHub · Add a comment — Comments on an issue or pull request. GitHub · Find issues — Issues by state, labels and date — one item each.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the steps' settings but cannot change them.

Before you start

A GitHub connection whose token has the repository and Issues: Read and write (fine-grained) or repo (classic) — see Connect GitHub.

Steps

Create an issue:

  1. Select + where the step should go. In the step picker, open Apps, select GitHub, then Create an issue. Or search GitHub.
  2. In Connection, choose your GitHub connection.
  3. In Repository, choose the repository — Repositories the connection reaches, as owner/name. For example consulace/billing-service. The list reads Loading your repositories… first.
  4. In Title, type the title — for example Invoice {{ trigger.number }} failed to send.
  5. Optional: in Body, the description — GitHub's Markdown.
  6. Optional: in Labels — Separate several with commas. Labels that do not exist yet are made. For example bug, billing.
  7. Optional: in Assignees — GitHub usernames, separated with commas.
  8. Optional: in Milestone — Optional — the milestone's number.
  9. Select Run this step to try it. This opens a real issue.

Update an issue:

  1. In the step picker, under GitHub, select Update an issue, and choose the Connection and Repository.
  2. In Number, the issue's number — 42, or {{ trigger.number }}. A # in front is fine.
  3. In State, choose Leave it, Open or Closed.
  4. Fill in only what should change: Title, Body, Labels (Replaces its labels. Empty leaves them.), Assignees (Replaces its assignees. Empty leaves them.).
  5. Select Run this step to try it.

Add a comment:

  1. In the step picker, under GitHub, select Add a comment, and choose the Connection and Repository.
  2. In Number, the issue's or pull request's number.
  3. In Comment, type the comment — GitHub's Markdown works.
  4. Select Run this step to try it.

Find issues:

  1. In the step picker, under GitHub, select Find issues, and choose the Connection and Repository.
  2. In State, choose Open, Closed or All. Open is chosen to begin with.
  3. Optional: in Labels, labels the issues must all have — Issues with all of these. Separate several with commas.
  4. Optional: in Changed since, a date — 2026-10-01. Only issues changed on or after it come back.
  5. Select Run this step to try it.

Output

Create an issue, Update an issue and each item from Find issues give the issue:

Field What it is
number The issue's number in the repository — what Update an issue and Add a comment take.
title, body Its title and description.
state open or closed.
url The issue's page on GitHub.
author The username of whoever opened it.
labels A list of its label names.
assignees A list of its assignees' usernames.
createdAt When it was opened.

Add a comment gives id and url — the comment's own address.

Good to know

  • Find issues gives one item for each issue, and the steps after it run once for each. Finding nothing gives no items, and the steps after it do not run. That is not a failure.
  • Find issues reads up to 100 issues, newest first, and leaves out pull requests — GitHub lists them among issues. So it can give fewer than 100 even when more exist.
  • A date in Changed since that cannot be read is ignored, and every issue comes back. Write it as 2026-10-01, or 2026-10-01T09:30:00Z for a time in UTC.
  • Update an issue and Add a comment also work on pull requests — on GitHub a pull request is an issue too, numbered in the same series.
  • Each item runs the step once. Ten items open ten issues.

If something goes wrong

What you see Why What to do
Number is not an issue or pull request number. Number holds something other than a whole number. Give a number such as 42 or #42.
Title is empty when the step ran — an earlier step may not have given the value it names. The title came out empty. Check the values it reads.
GitHub refused: Not Found. No issue with that number, or the token cannot see the repository. Check the number, and that the token has the repository.
GitHub refused: Validation Failed — … GitHub would not take a value — an assignee who cannot be assigned in this repository, or a milestone that does not exist. Fix the value GitHub names.
GitHub refused: Resource not accessible by personal access token. Check the connection's details on Connections. The token lacks Issues: Read and write. Add the permission in GitHub.
Could not load the repositories GitHub did not give the list. "What you set here is kept." Select Try again, or Reconnect if offered.