Integration · GitHub
Verified GitHub webhooks for your AI agent.
X-Hub-Signature-256 verification runs before persistence. Event type (from `X-GitHub-Event`) and delivery ID get extracted into `provider.eventType` and `provider.sourceId` so your routing rules can match on them directly.
Verification + metadata
What your agent receives
// Hooksbase verifies X-Hub-Signature-256 automatically
// Your agent receives:
{
"provider": {
"name": "github",
"sourceId": "d0e...",
"eventType": "issues",
"verified": true
},
"payload": { /* raw GitHub event */ }
}Routable metadata fields
Match on provider fields
Once GitHubverification is enabled, these fields are available to routing rules, delivery search, and your agent's payload.
- provider.name = "github"
- provider.sourceId = X-GitHub-Delivery (UUID)
- provider.eventType = X-GitHub-Event (e.g. "issues", "pull_request")
- provider.verified = boolean
Agent recipes
Common GitHub + agent patterns
Route `issues.opened` events to an agent that classifies, assigns labels, and asks clarifying questions.
Route `pull_request.opened` to an agent that runs initial review, flags risks, and posts comments.
Route `release.published` to an agent that drafts release notes from the tag + merged PRs.
Get started
Point GitHub at Hooksbase.
Configure the GitHub provider pack on a Hooksbase webhook, copy the ingest URL, paste it into your GitHub webhook settings. Every verified event lands with full provider metadata on the delivery.