wtf is webhook-debugger?

webhook-debugger is a tool for developers who work with webhooks, which are automated messages that one system sends to another over the internet, for example when a payment provider notifies your app that a purchase went through. The problem it solves is that webhooks are normally invisible: if something goes wrong, you cannot easily see what was sent, when it arrived, or replay it to test a fix. This project gives you a dashboard where you can inspect, replay, and monitor those incoming HTTP requests in real time. This particular build is described as Phase 1, the first of a planned three phases, and it covers the core logging experience: signing in with a magic link sent by email, creating an endpoint that can receive webhooks, viewing the logs of what arrived, and a dashboard to browse it all. Two bigger pieces are explicitly left for later phases: a Cloudflare Worker that will actually receive the incoming webhook traffic, and paid billing through a service called Creem. Replay, starring favorite requests, and search are planned for a third phase after that. Right now, since the email sending service is not wired up yet, the sign in tokens are returned directly in the API response instead of being emailed, which is meant purely for testing during this early stage rather than for real users. Under the hood it is built with Next.js and TypeScript on the frontend and backend, Supabase for the database with row level security rules protecting who can see what data, and it validates every piece of user input with a library called Zod so that bad data gets rejected before it causes problems. All the pages and API endpoints live inside a fairly standard Next.js project layout, with a separate folder holding the database schema and security policies. Because it is explicitly a Phase 1 build, this is best understood as an early foundation for a future paid webhook debugging product rather than a finished, ready to use service today. It is written in TypeScript.