We host on Hostinger — get up to 20% off your first plan.Get the link →
Referral link · we may earn a commissionReferral link — we may earn a commission at no extra cost to you.Download a working automation JSON
Can AI answer engines cite your site?
Outreach scripts that get replies
Find the 3 workflows costing you sleep
200+ prompts, ready to ship
12-month posting plan in 60 sec
Brand voice doc in 4 steps
Runway / Pika / Sora / Veo formats
Create a unique capture URL, point any webhook at it, and watch the actual request — method, headers, query, body — land here live within a couple of seconds. Then generate the matching n8n Webhook node in one click, so you go straight from "what does this payload look like" to a working node.
Updated August 2026
Why this tool exists
Every n8n, Zapier, or Make workflow that starts on a webhook has the same first step: fire the real event and look at what actually arrives. Field names drift from what the docs show. Nested objects show up where the docs implied a flat shape. Optional fields are sometimes present and sometimes not. You can guess at all of this from documentation, or you can just watch it happen once.
This tool gives you a unique capture URL the moment you load the page — no account, no API key. Point the real integration at it (GHL, Stripe, Calendly, a custom app, whatever), or hit the built-in test-fire button to confirm the loop works first. Every request that lands is redacted for anything that looks like a secret — cookie and authorization header values never make it past the capture endpoint — and shown here within a couple of seconds.
The part most request-bin tools stop short of: once you can see the real shape of the payload, this tool generates the matching n8n Webhook node plus a Set node pre-mapped to the fields you just captured, ready to import. You go from "I wonder what this sends" to a working starting node in the same tab.
Pair it with the Webhook Payload Builder when you need a sample shape before a real event exists yet, and the n8n Workflow Generator once you know what the trigger looks like and need the rest of the chain.
Waseem, building from Bali · info@skynetjoe.com
Comparison
| Feature | Webhook Inspector | webhook.site |
|---|---|---|
| Price | Free, no signup | Free tier + paid plans |
| Bin lifetime | 24h, or until the server restarts (stated up front) | Longer-lived, dedicated service |
| n8n node generation | Yes — one click from any captured request | No |
| Header redaction | Cookie/Authorization values redacted automatically | Shown as received |
| Best for | Debugging one integration you're actively wiring right now | Long-running or team-shared inspection |
Feature comparison based on webhook.site's publicly documented free tier as of August 2026. Verify current details on their site — third-party pricing and features change.
Quick answers
24 hours from creation, and that's the honest ceiling — not a guarantee. This tool runs as a single Node process with in-memory storage, the same way the rest of skynetjoe.com's live tools do. If the server restarts (a deploy, a crash, routine maintenance), every bin clears immediately, well before 24 hours. Don't point a production webhook here and walk away — it's for debugging in the moment, not for durable delivery.
For testing and debugging, yes. For anything carrying real secrets, be careful: cookie and authorization header VALUES are redacted to "[redacted]" before they're ever stored, and the raw body is capped at 64KB, but the rest of the payload — including whatever fields your app sends — is stored as-is and shown in your browser tab. Treat it like any other request-bin tool: fine for shape-checking a Stripe or GHL test event, not for piping production PII through.
Only whoever has your bin's URL. The bin ID is a 96-bit random token — unguessable by brute force — and that ID is the only access control; there's no login. Anyone you share the capture URL with can also see what lands in it, same as any request-bin tool.
Simplicity and reliability on a single Node process without a pub/sub layer. Short-polling every 2.5s is close enough to real time for debugging a webhook, costs nothing extra to run, and pauses automatically when you switch tabs so it isn't hammering the server in the background.
An importable n8n workflow JSON snippet: a Webhook node pre-configured with the captured request's HTTP method and a placeholder path, plus a Set node that maps the top-level fields from the captured body. Paste it into n8n via Workflows → Import from File (or paste-as-JSON) and you have a working starting point instead of a blank canvas. No credentials are ever embedded.
For a quick shape check while wiring an n8n workflow, this tool does the same core job — plus the n8n node generation those tools don't offer. It doesn't replace a dedicated, always-on request-bin service for long-running integrations: this one is explicitly ephemeral (see the 24-hour / restart-clears-it answer above), because it's running on the same single Node process as the rest of this site, not a dedicated queue-backed service.