GitHub
The GitHub integration lets Helios agents search and call the entire GitHub REST API to manage repositories, automate pull requests and issues, drive GitHub Actions, and run automatically on repository events.
What your agents can do
Helios agents don't choose from a fixed menu of GitHub actions. They semantically search GitHub's entire REST API and call any endpoint directly, with authentication injected server-side - so anything the GitHub API can do, an agent can do on your behalf.
- Open, review, comment on, and merge pull requests
- Triage issues - label, assign, close, and reply
- Read and write repository contents, branches, tags, and releases
- Kick off and inspect GitHub Actions runs, check runs, and workflow status
- Manage collaborators, teams, and repository settings
- Clone a repo and work directly in its code (see Pinned resources)
Authentication
| Method | Type | Description |
|---|---|---|
| Helios GitHub App (Recommended) | GitHub App | Install with a single redirect; Helios manages tokens |
| Personal Access Token | Token-based | You supply a PAT with the scopes your agents need |
| BYO GitHub App | GitHub App | You supply your own App's ID, private key, and install |
See Integration authentication for how credentials are stored and injected.
Helios GitHub App (Recommended)
Connecting through the Helios GitHub App is the fastest path. When you create the integration, Helios redirects you to GitHub to install the app and pick the repositories or organization it can access. Tokens are minted and refreshed for you - you never handle a credential.
For an organization or enterprise install, each user who wants their agents to act must also complete a one-time per-user authorization before those agents can use the integration.
Personal Access Token
You can also connect with a Personal Access Token (PAT) scoped to your use case.
- Go to GitHub Settings → Developer settings → Personal access tokens.
- Click Generate new token → Generate new token (classic).
- Select the scopes your agents need (e.g.
repo,workflow,read:org). - Copy the generated token and paste it into Helios.
- Save the integration.
BYO GitHub App
Bring your own GitHub App when you need custom branding or your own permission model.
- Go to GitHub Settings → Developer settings → GitHub Apps.
- Click New GitHub App and configure its permissions and events.
- Generate and download a private key.
- Install the app on your repositories and note the installation ID.
- In Helios, provide the App ID, private key, and installation ID.
Supported deployments
The integration works across GitHub deployments. Select the matching API version when you connect:
| Deployment | API version | Notes |
|---|---|---|
| GitHub.com | 2022-11-28 | Default for github.com |
| GitHub Enterprise Cloud | ghec | Enterprise-hosted cloud |
| GitHub Enterprise Server | ghes-3.17 | Self-hosted - you must supply your GHES base URL |
Triggers
GitHub is one of only three integrations that emit event triggers into Helios, so a Workflow can run an agent automatically when something happens in a repository. Every event requires a repository (repoId) filter; some events support additional filters.
| Event | Filters |
|---|---|
pull_request.opened | repository |
pull_request.closed | repository |
pull_request.synchronize | repository |
pull_request.labeled | repository, label (glob) |
issues.opened | repository |
issues.closed | repository |
issues.labeled | repository, label (glob) |
push | repository, branch (glob, required) |
tag.created | repository, tag name (glob) |
release.published | repository |
workflow_run.completed | repository, workflow name (glob), conclusion |
issue_comment.created | repository |
Filter semantics: multiple values for the same field are OR'd; different fields are AND'd. Glob patterns support *, ?, **, [abc], and {a,b}.
See Triggers for how to attach these to a Workflow.
Pinned resources
GitHub is the only integration that supports pinned resources. You can attach specific repositories to a chat or a Workflow. Helios then mints a short-lived, repo-scoped installation token and injects it at the network layer, so the agent can git clone and work in the repo without ever seeing a credential.
Learn more in Integration resources.
Last updated on
Authentication
Connect a service with a Helios-managed OAuth app, your own OAuth app, or an API key. Credentials are envelope-encrypted and never reach the agent.
Slack
The Slack integration lets Helios agents search and call the entire Slack API to post messages, manage channels, work with files and canvases, and run automatically on new messages.