Sign in Start free

Webhook Guardian monitors GitHub webhook delivery failures by polling the GitHub API delivery logs every 5 minutes via OAuth. You get a Slack or email alert within 5 minutes of any failed delivery to your CI/CD pipelines, deployment triggers, or automation endpoints.

GitHub integration

Know when your GitHub
webhooks fail

A failed push event can silently break your CI pipeline for days. Webhook Guardian alerts you within 5 minutes — so your deployments don't go dark without you knowing.

Connect GitHub free See pricing
  • 14-day free trial
  • repo + admin:repo_hook scope
  • Setup in 2 minutes
How it works

How does Webhook Guardian read GitHub delivery logs?

We use the GitHub API to read the delivery log entries GitHub already stores for every webhook attempt — every 5 minutes, without touching your code.

  1. 01

    Connect via GitHub OAuth

    Authorize via GitHub's OAuth flow. We request repo and admin:repo_hook scopes — enough to read delivery logs, nothing more. No code access.

    # Scopes requested
repo · admin:repo_hook · No write access to code
  2. 02

    We poll delivery logs every 5 minutes

    GitHub stores delivery logs for 72 hours. We read them via the API every 5 minutes across all your configured webhooks — repo and org level.

    # Coverage
repo webhooks · org webhooks · all event types
  3. 03

    Alert fires with delivery UUID and payload

    The Slack message includes the event type, repository, delivery UUID, HTTP response code, response body excerpt, and a direct link to redeliver.

    # Example: push (main)
delivery: b3f1c0a8 · 503 · timeout · redeliver →
  4. 04

    Replay directly from the alert

    Click the replay link in Slack or from the dashboard to redeliver the event from GitHub to your endpoint. Logged with full audit trail.

    # Logged
timestamp · endpoint · response · outcome
What we catch

Which GitHub webhook failures does it detect?

Every failed delivery across all event types — push, PR, deployment, workflow, and more.

push

Failed push events break CI triggers, deployment pipelines, and code-sync automations.

pull_request

Missed PR events break review bots, status checks, and automated label workflows.

workflow_run

Failed workflow events break downstream automation that depends on CI completion signals.

deployment

Missed deployment events leave environments in unknown state and break release tracking.

FAQ

GitHub webhook monitoring — questions answered

How do GitHub webhook delivery logs work?
GitHub stores a delivery record for every webhook attempt — event type, UUID, response code, response body, and timestamp — for 72 hours. Webhook Guardian reads these logs via the API every 5 minutes to detect failures the moment they happen.
What GitHub permissions does Webhook Guardian request?
repo and admin:repo_hook scopes. These allow reading delivery logs. We never request write access to repositories, code, issues, or pull requests.
Which GitHub event types does it monitor?
All events configured on your repository or organization webhooks — push, pull_request, workflow_run, deployment, create, delete, and any others. No extra setup required.
Can it monitor GitHub organization webhooks?
Yes. Both repository-level and organization-level webhooks are supported. Organization webhook monitoring is available on Pro and Business plans.

Start monitoring GitHub webhooks free

Connect in 2 minutes. Know when your CI pipeline stops receiving events.

Start free trial All integrations