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.
Something happens in the repository
Someone opens an issue, comments, opens a pull request or leaves a review.
issues.openedconnic 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-256Linked 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.createdThe 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.
{
"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.
{
"title": "EUR totals are rounded twice at checkout",
"body": "Orders in EUR are one cent off since 2.14.0."
}{
"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.
{
"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"
}{
"body": "Likely the refunds service. Which order ID and browser?"
}A pull request opens, and the agent comments on what its description is missing.
{
"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"
}{
"body": "Missing: test notes and a linked issue."
}Your helpdesk sends a bug report, and the agent turns it into a GitHub issue.
{
"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%."
}{
"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.
{
"service": "checkout-api",
"error": "Order ord_88412 has no currency",
"first_seen": "2026-11-16T09:12:04Z",
"events_last_hour": 214
}{
"title": "checkout-api: orders without a currency fail",
"body": "214 errors in the last hour, first seen at 09:12 UTC."
}GitHub FAQ
More connectors
Apache Kafka
Consume topics to trigger agents and produce results back to topics under the source message key.
Inbound · Outbound
Google Sheets
Run an agent on every new row in a spreadsheet and append its results as rows. connic signs in with your own service account.
Inbound · Outbound
HTTP Webhooks
Run an agent on any HTTP request with JSON, form data, or file uploads. No glue server is required.
Inbound · Outbound · Sync
Pipedrive
Run an agent when deals, leads, people or organizations are created, updated or deleted in Pipedrive. It adds its result as a note to the record.
Inbound · Outbound
Twilio Messaging
Receive SMS, MMS, WhatsApp, and RCS messages with an agent. Send replies, media, and WhatsApp templates through your Twilio account.
Inbound · Outbound
Twilio Voice
Answer and place calls on your Twilio number with a voice agent. Use its tools and knowledge throughout one continuous conversation.
Sync · Outbound