GitHub push events, PR webhooks, and deployment notifications routed reliably to your CI/CD system — with automatic retry if Jenkins, ArgoCD, or your deploy service is temporarily unavailable.
The HTTP webhook protocol has no persistence, no retries, and no observability — and it shows.
Your Jenkins server is restarting after an update. GitHub sends the push event, gets 503, and does not retry sufficiently. The build never starts. The team discovers it when a deployment doesn't happen.
ArgoCD is unreachable during a network partition. GitLab sends the release.published event — it's gone. The deployment rollout never triggers and the release is stale.
You have GitHub webhooks going to Jenkins, GitLab CI, and a Slack bot — three different systems with three different logs. When something breaks, correlating which event triggered which action is a detective exercise.
From raw HTTP POST to guaranteed delivery — set up in under 10 minutes.
Create a Source with the GitHub or GitLab preset. GetHook auto-configures X-Hub-Signature-256 or X-Gitlab-Token verification. Copy the ingest URL to your repository webhook settings.
POST /v1/sources
{ "name": "github-monorepo", "auth_mode": "hmac", "verification_config": { "header": "X-Hub-Signature-256", "secret": "github-webhook-secret" } }Push events to your CI server, release.published to your deploy system, and pull_request.merged to your Slack bot — using simple glob pattern routes.
POST /v1/routes
{ "event_type_pattern": "push", "destination_id": "dest_jenkins" }
{ "event_type_pattern": "release.published", "destination_id": "dest_argocd" }
{ "event_type_pattern": "pull_request.*", "destination_id": "dest_slack" }CI system was down during a push? Replay the push event after recovery. ArgoCD missed a release? Replay the release.published event. No manual re-pushing to git required.
POST /v1/events/{id}/replay
# Re-triggers the CI build or deploy
# Original GitHub payload is re-delivered verbatim5-attempt retry with exponential backoff means a Jenkins restart or ArgoCD pod eviction won't cause a missed build.
A single push event can simultaneously trigger your CI server, update your deployment dashboard, and post to Slack — independently.
Pre-configured HMAC verification for all major source control and registry providers. No header documentation required.
All CI/CD trigger events in one place, with delivery status per destination. Correlate a git push to a build to a deployment in a single view.
When a CI system recovers from an outage, replay all missed push and release events to catch up without manual intervention.
Route push to CI, release.published to deploy, pull_request.* to PR bot. One ingest endpoint, multiple automation targets.
Replace ad-hoc HTTP calls between microservices with durable webhook delivery. Fan-out from one source to many consumers, route by event type, and guarantee delivery.
Failed payments, new signups, system alerts — route each event type to Slack, PagerDuty, email, and SMS simultaneously, with guaranteed delivery and automatic retry.
Webhook events are the nervous system of modern AI agents. GetHook ensures every trigger — document uploads, user messages, tool responses — reaches your agent reliably, with replay for debugging.
Up and running in minutes. No credit card required. Connect your first source and see events flowing in real time.