Help center menu

APP GUIDE · GITHUB

Automate GitHub with AIVane

AIVane can open GitHub issues, comment on issues and pull requests, and list your repositories and a repository's issues. Use it to turn what an automation finds on a website or in a spreadsheet into issues, or to report a check's result where your team already works.

  • Runs in: Desktop app

Where it runs and what you need

Where these steps run
AIVane Cloud, from your browserUse the desktop app: GitHub steps run in automations on your computer.
Desktop app, on your computerYes, in the AIVane desktop app for Windows. Your computer has to be on while the automation runs.

What you need

  • A GitHub account and the credential described under Connect
  • Any AIVane plan: connecting apps is included in every plan, including Free
  • For runs on your computer, the AIVane desktop app

See plans and pricing

Connect GitHub

  1. In the AIVane desktop app open Settings, then Connections, and choose Add connection.
  2. Under Connect with an API key or token, find GitHub and choose Choose.
  3. Keep or change the Name, then enter your personal access token (fine-grained or classic). The form's Where do I find this? link opens GitHub's page for creating it.
  4. Choose Save, then Test on the new connection: Works means GitHub accepted it.

Change or remove it

If GitHub stops accepting the secret, the connection shows Secret rejected. Open its menu in Settings, Connections and choose Update secret to enter a new one, or Disconnect… to remove it from this computer. To retire the credential itself, revoke it at GitHub.

What AIVane can do with GitHub

  • List the repositories you can accessReturn one page of the repositories the token user can access.In the editor: List my repositories · Runs in: desktop appInputs: visibility, affiliation, sort, perPage, page (optional)
  • List the issues of a repositoryReturn one page of issues of a repository. GitHub also returns pull requests here; they have a pull_request field.In the editor: List issues · Runs in: desktop appInputs: owner, repo (required); state, labels, assignee, since, sort, direction, perPage, page (optional)
  • Open an issueOpen an issue in a repository.In the editor: Create issue · Runs in: desktop appInputs: owner, repo, title (required); body, labels, assignees (optional)
  • Comment on an issue or pull requestAdd a comment to an issue or pull request.In the editor: Add issue comment · Runs in: desktop appInputs: owner, repo, issueNumber, body (required)

Add these as steps in the Flow editor: choose Insert step, add a Connector action step, then choose GitHub, the action and your GitHub connection, and fill in its inputs. The browser and desktop parts of the automation can come from a recording or from Describe a task. Add new GitHub steps in the Flow editor; the AI assistant keeps the app steps an automation already has when it changes it. To check a saved connection, choose Test on it in Settings, Connections.

IDEAS

Automations you could build

Ideas, not ready-made automations, unless a link says so. Each uses only the steps above and browser or spreadsheet steps.

Open your service's public status page, read its status, and open an issue in your repository with the page's text when it doesn't say everything is working.

List the open issues labeled bug in a repository and save them to an Excel file for a weekly report.

After an automation has tested a form on your website, comment on the tracking issue with what it saw.

Limits

  • Steps work with repositories on github.com.
  • Listing issues also returns pull requests; they carry a pull_request field you can filter on.
  • Labels and assignees of a new issue are set only when the token's user has push access to the repository.
  • A list returns at most 100 items per page; read further pages with the page input.
  • New steps can use the GitHub actions listed on this page.
  • GitHub steps run in automations on your computer with the desktop app; keep the computer on while they run.

GitHub questions

Which token does AIVane need?

A GitHub personal access token, fine-grained or classic, that can access the repositories your automation uses. Create it in GitHub's settings under personal access tokens.

Can AIVane comment on pull requests?

Yes. Commenting works on issues and pull requests alike: give the step the pull request's number.

Can AIVane find issues with a given label?

Yes. List issues takes label names, an assignee, a state and a since time, so a step can read only the issues the automation needs.

Can AIVane open an issue with labels and assignees?

Yes, when the token's user has push access to the repository. Give the step the label names and the logins to assign.

Last checked November 18, 2026 against the current AIVane release. Something different in your app? Contact support.

YOUR OWN TASK

Want help automating your own task?

Our first users can ask for hands-on help: one website task, one sheet, and a week of watching it run.

Get help automating a task ↗