Integrations · Projects & issues

GitHub in the conversation.

Where the code, the issues and the pull requests live. Connect it once and your copilot works with repositories, issues, pull requests, comments and releases without leaving the thread — and your workflows can act on it while the customer is still typing.

Start free trial →All integrations

No credit card required · 7-day free trial

GitHub
Projects & issues
01 · COPILOT

Ask for it in plain language. It does the GitHub part.

Copilot rides inside the inbox. With GitHub connected it reads repositories, issues, pull requests, comments and releases and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

  • Search issues and pull requests in a repository
  • Read an issue or PR with its discussion
  • Open an issue with a body you generate
  • Comment on an issue or a pull request
  • Read a release and its notes

What a specific connection exposes is decided by GitHub, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.

02 · WORKFLOWS

Something happens in GitHub. A workflow starts.

Once GitHub is connected, its events show up in the workflow editor's trigger picker, and the fields the event carries become variables every later step can read — so the message you send is written from what actually happened.

  • An issue is opened or closed
  • A pull request is merged
  • A release is published

The picker is the authority on which events your GitHub connection publishes — these are the kinds that apps of this sort emit.

03 · THE AI AGENT STEP

One step that decides which GitHub tools to call.

A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.

You declare the output

The rows you name become the variables downstream steps read, so a branch can test what GitHub said.

You cap the effort

A step budget and a model tier per node — the loop stops where you told it to.

Only what you switched on

The loop can call the GitHub tools you left enabled and nothing else.

What teams do with it

Two ways GitHub earns its connection.

01

Report the bug where it gets fixed

The conversation becomes a GitHub issue in the right repository, with the reproduction the customer described already written up.

02

Ship notes that reach customers

A workflow fires on a published release and messages the customers whose conversations were linked to what shipped.

Setup

Connect GitHub in about a minute.

  1. 1

    Open Settings → Apps

    It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.

  2. 2

    Find GitHub in Browse

    The catalogue runs to hundreds of apps and is searchable. Connect GitHub from its card.

  3. 3

    Authorize with your own GitHub account

    You sign in on GitHub's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.

  4. 4

    Choose the tools it may call

    Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.

Open Settings → Apps →

GitHub questions.

How do I connect GitHub to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for GitHub. Connecting it opens GitHub's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.
What can Cloodot do in GitHub?
Work of this kind: search issues and pull requests in a repository; read an issue or pr with its discussion; open an issue with a body you generate; comment on an issue or a pull request; read a release and its notes. The exact list depends on what your GitHub account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which GitHub tools Cloodot may use?
Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only GitHub connection is a matter of leaving the writes off.
Can an event in GitHub start a Cloodot workflow?
Yes. Events like an issue is opened or closed, a pull request is merged, a release is published appear in the workflow editor's trigger picker once GitHub is connected, and the event's own fields become variables the rest of the workflow can read.
Who in my team can connect GitHub?
Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the GitHub account that authorized it, so a projects & issues connection is only ever as broad as the account behind it.
More projects & issues

Rarely just one app.

JiraAtlassian's issue tracker, and the queue engineering actually works from.LinearA fast issue tracker built for product teams that live in the keyboard.AsanaWork management for teams that plan in projects and tasks rather than tickets.TrelloBoards, lists and cards — the simplest thing that still works for a small team’s queue.ClickUpA work platform that tries to be the tracker, the doc and the goal board at once.monday.comA visual work OS where a team models its own process as boards and columns.
Browse every integration
See it on your own inbox

Try the whole thing, today.

Start free. Connect a channel, train an agent on your own content, and you'll have a working deployment in your inbox the same afternoon.

Start free trial →Sign in