Integration · GitHub
Verified GitHub webhooks for your AI agent.
Hooksbase verifies each GitHub webhook signature before persisting the delivery, stamps queryable provider metadata (event type, source ID, verified flag) on the event, and routes it to your AI agent — no webhook plumbing to build.
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.
Frequently asked questions
How do I verify GitHub webhooks with Hooksbase?
Add the GitHub provider pack to a Hooksbase webhook and paste your GitHub webhook secret. Hooksbase verifies the `X-Hub-Signature-256` header against that secret before persisting the delivery, so unsigned or tampered payloads never reach your agent.
Does Hooksbase check the GitHub signature before my agent sees the event?
Yes. Hooksbase validates `X-Hub-Signature-256` before the delivery is persisted and sets `provider.verified = true`. Your agent only receives GitHub events whose HMAC signature already matched your secret.
Which GitHub event types can I route on with Hooksbase?
Hooksbase reads the `X-GitHub-Event` header into `provider.eventType` (for example `issues` or `pull_request`), so you can route on any GitHub event type directly. The `X-GitHub-Delivery` UUID is captured as `provider.sourceId` for deduplication and tracing.
Can I send GitHub events to multiple destinations from Hooksbase?
Yes. Hooksbase can route one verified GitHub event to several typed destinations at once — for example a triage agent over HTTP plus AWS SQS or EventBridge — each carrying the same provider metadata.
Can I replay a GitHub webhook delivery in Hooksbase?
Yes. With 30-day delivery-detail retention and deterministic replay from the persisted dispatch snapshot, Hooksbase lets you re-deliver a verified GitHub event to your agent after a code fix without reconfiguring the GitHub webhook.
What is Hooksbase?
Hooksbase is event infrastructure for AI agents. It ingests events over four channels — HTTP, email, HTML form, and scheduled cron — verifies them, routes them by rule, runs versioned Automations in the event path, and delivers them to HTTP and cloud destinations (AWS SQS, AWS EventBridge, GCP Pub/Sub, and S3-compatible storage) with retries, strict ordering, Standard Webhooks-compatible signing, deterministic replay, and a dead-letter path. It is a hosted service, runs on Cloudflare Workers, is operated at hooksbase.com, and is not affiliated with — and shares no code or ownership with — other similarly named webhook, hook, or tunnelling tools.
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.