Skip to main content
connic

GitHub

Run connic agents on issues, comments and pull requests in your GitHub repositories. Agents comment back or open new issues.

Modes
Inbound, Outbound
Set up in
Dashboard or connectors/*.yaml
Documentation
GitHub docs
Publisher
By connic

Answer issues and pull requests

When something in the repository matches an inbound connector's events, every agent linked to it starts. An outbound connector on the same Connection comments the result on the issue or pull request.

Pick events and actions
issues reacts to every action, issues.opened only to new issues. Issues, comments, pull requests, reviews and review comments are supported.
Several connectors per repository
Watch issues with one and pull requests with another, or use one per environment. An event reaches every connector that matches.
No loops, no double runs
The app's own comments and issues are ignored, and an event that GitHub delivers again doesn't start a second run.
  1. Something happens in the repository

    Someone opens an issue, comments, opens a pull request or leaves a review.

    issues.opened
  2. connic checks and confirms the event

    It verifies the signature with the app's webhook secret and answers GitHub right away, well within its 10 seconds.

    X-Hub-Signature-256
  3. Linked agents start

    The run gets the event and action, the issue or pull request number and title, the text, a link and the sender.

    issue_comment.created
  4. The answer lands as a comment

    An outbound connector on the same Connection comments on the issue or pull request the run started from.

Create the GitHub App from a prepared manifest

connic prepares the app with its webhook URL, three permissions and five events. You create it on GitHub under your account or organization, and GitHub hands connic its credentials.

Your app, kept private
The app belongs to your GitHub account or organization and can only be installed there. Create one Connection per account or organization.
Three permissions
Issues and pull requests read and write, metadata read. The app only sees the repositories you install it on.
Nothing to paste
GitHub hands the app's ID, private key and webhook secret to connic when you create the app. Finish within an hour of starting on GitHub.
github-app-manifest.json
{
  "name": "Acme Agents",
  "description": "Connects repositories to agents on connic.",
  "public": false,
  "hook_attributes": {
    "url": "<webhook-url>",
    "active": true
  },
  "default_permissions": {
    "issues": "write",
    "pull_requests": "write",
    "metadata": "read"
  },
  "default_events": [
    "issues",
    "issue_comment",
    "pull_request",
    "pull_request_review",
    "pull_request_review_comment"
  ]
}

Comment on issues or open new ones

An outbound GitHub connector posts the agent's output, whether the run answers an issue or pull request or comes from another connector or a schedule.

Routing
An issue_number in the output wins. Without one, a run started from an issue or pull request on the same Connection comments there, and any other run opens an issue in the connector's repository.
Three ways to send
Send after every completed run, give the model a tool to call, or call send_connector from middleware when your code decides.
Rate limits handled
When GitHub rate-limits a comment or issue, connic waits and sends it again.
output.json
{
  "title": "EUR totals are rounded twice at checkout",
  "body": "Orders in EUR are one cent off since 2.14.0."
}
connector-payload.json
{
  "body": "Reproduced on main: the total is rounded twice.",
  "issue_number": 42
}

Where GitHub fits

Pick a setup to see what reaches the agent and what it posts back to GitHub.

Someone opens an issue, and the agent asks for missing details and names the likely area.

New issue
Inbound GitHub
issue-triage
Comment on the issue
github-payload.json
{
  "event": "issues",
  "action": "opened",
  "repository": "acme/api",
  "number": 418,
  "title": "Refund button does nothing",
  "text": "Clicking Refund on an order shows no error and no refund.",
  "url": "https://github.com/acme/api/issues/418",
  "sender": "octocat"
}
output.json
{
  "body": "Likely the refunds service. Which order ID and browser?"
}

A pull request opens, and the agent comments on what its description is missing.

New pull request
Inbound GitHub
pr-checklist
Comment on the pull request
github-payload.json
{
  "event": "pull_request",
  "action": "opened",
  "repository": "acme/api",
  "number": 421,
  "title": "Round EUR totals once",
  "text": "Moves rounding from the cart to the payment step.",
  "url": "https://github.com/acme/api/pull/421",
  "sender": "octocat"
}
output.json
{
  "body": "Missing: test notes and a linked issue."
}

Your helpdesk sends a bug report, and the agent turns it into a GitHub issue.

Helpdesk
Inbound webhook
bug-reporter
New issue in acme/api
ticket.json
{
  "ticket_id": "T-20931",
  "customer_id": "C-1042",
  "subject": "Invoice PDF shows the wrong VAT rate",
  "message": "Since Monday our invoices show 16% instead of 19%."
}
output.json
{
  "title": "Invoice PDF uses 16% VAT instead of 19%",
  "body": "Reported in T-20931: invoices since Monday use 16%."
}

Your monitoring reports a new error, and the agent opens an issue with what it knows.

Error monitoring
Inbound webhook
error-triage
Issue for the error
alert.json
{
  "service": "checkout-api",
  "error": "Order ord_88412 has no currency",
  "first_seen": "2026-11-16T09:12:04Z",
  "events_last_hour": 214
}
output.json
{
  "title": "checkout-api: orders without a currency fail",
  "body": "214 errors in the last hour, first seen at 09:12 UTC."
}

GitHub FAQ

You do. connic prepares the app, and you create it on GitHub under your personal account or an organization you own. The app is private, so only that account can install it. Create one Connection per account or organization.

Issues and pull requests with read and write access, plus repository metadata, and only in the repositories you install it on. It receives events for issues, comments, pull requests, reviews and review comments.

No. When you create the app, GitHub hands its ID, private key and webhook secret to connic, and connic sets the webhook URL itself. Finish the setup within an hour of starting on GitHub.

No. Comments and issues the app writes itself are ignored, so an agent doesn't start itself again.

Yes, with type: github and the name of a GitHub Connection. The Connection itself, with its GitHub App, is set up in the dashboard; until then, the deploy fails.