Built an n8n webhook trigger and want to see what’s hitting it before you wire the rest of the workflow? Same problem I had three weeks ago. So here’s a free webhook receiver. Get a unique URL, point anything at it, see every request in real time.
How to use this
Open the tool above. It generates a unique URL for you automatically. Copy it. Point a service, an n8n workflow, a Zapier zap, or a curl command at that URL. Every hit shows up below with the method, the headers, the body, and the source IP.
The URL persists as long as the page tab stays open. Bookmark it if you need it later. Hit “Generate new URL” if you want a fresh one. Hit “Clear hits” to wipe the history.
Why I built this instead of using webhook.site
Webhook.site is great. I used it for ages. The reasons I built my own come down to two things. First, I wanted a tool I could embed on the blog and brand to match jen8n.com. Second, I wanted full control over the data. Webhook.site is a third-party service, and any payload your tools send to it lives on their servers. Mine lives on my Cloudflare D1 database, which I control. If you’d rather use webhook.site, do. The tool above is just an option.
Common patterns I use it for
Testing whether an external service fires its webhook on the event you expect. Stripe webhooks especially. Set the webhook URL to one of these test URLs, trigger the event, see what arrives. Then you know exactly what fields are in the payload before you build the n8n workflow that parses them.
Debugging an n8n workflow that’s supposed to forward a webhook somewhere else. Point both your inbound webhook trigger and a copy of the tester URL at the same source. Compare what arrives where.
Checking whether a scheduled job in another tool fires correctly. Some tools’ “test webhook” buttons don’t actually send the real payload. Pointing the real schedule at the tester for one cycle tells you exactly what gets sent in production.
FAQ
How long do hits stay?
Forever, until you click “Clear hits.” The tool stores them in a Cloudflare D1 database tied to the random token in your URL. If you lose the token (close the tab without bookmarking), the hits are still there but you’d need the exact token to retrieve them.
Can I receive form submissions on this?
Yes. The tool accepts every HTTP method and content type. Form submissions, JSON, multipart uploads, anything. The body shows in the hit detail.
Is there a rate limit?
Cloudflare’s default limits apply, which work out to thousands of requests per minute. For normal webhook testing you’ll never hit them. If you’re load testing, use a proper load testing tool.
Does this work for OAuth callbacks?
The receiver part does. Many OAuth flows expect a redirect after the callback though, which the tester doesn’t simulate. For full OAuth testing, you want a tool that can both receive the callback and redirect downstream. This is for inspection, not orchestration.
Can I share a URL with someone else?
Yes. Anyone with the URL can hit your endpoint and view the hits. Don’t use it for sensitive data or anything you don’t want a stranger seeing.
One thing this saves me every time
I no longer spin up an n8n webhook trigger just to see what some external service sends. Saves me a workflow slot and saves me the mental load of “is the workflow broken or is the payload weird?” Now I check what the payload looks like first, then build the workflow knowing what I’m parsing.
Workflow blueprints, n8n breakdowns, and tool reviews land in the newsletter as I write them. Subscribe so you don’t miss the next one.
More tools I’ve built
If this one’s useful, the rest of the toolbelt might be too:
- Cron Expression Builder — If you’re triggering this on a schedule, build the cron expression here first.
- Automation ROI Calculator — Before you wire up a full workflow around this webhook, check whether the build pays for itself.
- n8n Cost Calculator — When your stack of automations starts adding up, compare cloud vs self-host.