A missed push webhook is a missed deploy. Not fun.
GitHub fires webhooks on every push, pull request, release, issue and discussion. CI/CD pipelines and deploy systems rely on them. Miss one and your pipeline doesn't run — usually noticed when someone asks where their change went. WebhookFlow makes sure every GitHub event lands.
Why GitHub webhooks need extra care
High volume in active repositories
An active open-source repo or busy monorepo can produce hundreds of events per day — especially with push events on feature branches and CI check-runs. One brief outage on your side and you miss dozens of events.
GitHub doesn't retry forever
If a delivery fails GitHub retries a few times with increasing intervals, then stops. No automatic catch-up if your server was offline for half a day during a release window.
Signature validation via HMAC
GitHub signs webhooks with HMAC-SHA256. A misconfigured secret or body-encoding difference leads to rejected events — often silently, with no clear error on your side.
What WebhookFlow specifically does for GitHub
Accept instantly, feed your pipeline calmly
WebhookFlow returns 200 to GitHub within milliseconds. We then forward the event to your CI/CD system or deploy controller at a pace it can handle. No overflowing queue, no lost push.
Persistent retries during downtime
Runner or orchestrator briefly unreachable? WebhookFlow holds events and retries for hours. As soon as your side is back the system receives all missed push and release events in order.
Central HMAC validation
Configure your GitHub webhook secret once in WebhookFlow. We validate every incoming request per the GitHub spec and reject mismatches before they reach your infrastructure.
Filter by event type
GitHub sends many event types to one URL. WebhookFlow can forward only "push" to your deploy system, and "issues" or "discussion" to your notification service. No more filter logic in your application.
Frequently asked questions about GitHub webhooks
Does this work with repository and organization webhooks?
Yes. WebhookFlow accepts webhooks from any level — single repository, organization-wide or GitHub App. Configuration is identical: set the payload URL to the WebhookFlow endpoint and copy the secret.
Can I replay webhook deliveries?
Yes. GitHub offers a "Redeliver" button in webhook settings, but it doesn't scale to hundreds of events. In WebhookFlow you see per event whether it was forwarded and the response your server gave — replay with one click, or programmatically via API.
Is this overkill for a hobby project?
For hobby CI on one repo this is probably overkill. For a team relying on CI speed and deploy reliability, or a SaaS platform processing customer GitHub events, every missed event counts.
How do I set this up from GitHub?
In your repository or organization settings go to Webhooks, add a new webhook with the WebhookFlow URL and your secret. Select the events you want to receive (or everything with "Send me everything"). From that point each call routes through WebhookFlow.
Never miss a push event again
WebhookFlow is in development and looking for beta users. Sign up for early access.