Webhooks are awkward to develop against. The sender lives on the internet, your code lives on localhost:3000 , and the interesting bugs (retries, signature failures, out-of-order events) only show up with real traffic.
These eight free tools cover the whole loop: see what's being sent, get it onto your machine, and replay it until your handler is right. Most have paid tiers, but the free tier is enough for development.
Inspect: see the raw request first
Before writing a handler, look at exactly what the sender delivers: headers, body and encoding. It saves you from guessing at the payload shape.
1. webhook.site
Open the site and you get a unique URL. Paste it into the sender's webhook settings and every request shows up live with full headers and body.
Use it when: you're integrating a new provider and want to see real payloads before writing any code.
Watch out: the URLs are public by default. Don't send production data with customer details through it.
2.…