Free Tools /Development
Webhook Sample Payload Generator
Pick a real event type from Stripe, Shopify, HubSpot, or Typeform, get a realistic sample payload, and optionally fire it directly at your own test webhook URL.
Sends a real POST request with this JSON body directly from your browser to the URL above. Nothing passes through PURIST's servers.
How this tool works
Real payload shapes, not guesses
Each sample matches the actual structure that service sends for that event type: field names, nesting, and typical data types, so your workflow logic is tested against something realistic.
Multiple event types per service
Pick the specific event (new order vs. refund vs. subscription cancelled) rather than one generic shape, since your workflow branches differently for each.
Send it live to your own test webhook
Paste your n8n test webhook URL and fire the generated payload directly at it with one click, no need to copy-paste into a separate tool or write a curl command by hand.
Frequently asked questions
Will this exactly match what the real service sends?
It matches the commonly documented structure for that event as of when this tool was built. Providers occasionally add fields or restructure payloads; always validate against the specific version noted in that provider's current webhook documentation for anything going to production.
Can I send this to any URL, or only n8n?
Any URL that accepts a POST request with a JSON body, including an n8n Webhook node's test URL, a webhook.site style inspector, or your own API endpoint. This is a standard browser fetch() call, not something n8n-specific.
Why does my n8n workflow fail with this test payload even though it looks right?
Most commonly a signature verification step, some providers (Stripe especially) sign real webhook requests with a header your workflow checks. A synthetic test payload will not carry a valid signature, temporarily bypass or mock that check while testing with sample data.
Does sending the payload from this page have any CORS restrictions?
Sending to a webhook endpoint that accepts requests from any origin (most n8n and webhook-testing tools do) works fine. An endpoint with strict CORS policy limited to specific origins will reject the browser-based request; use a tool like curl or Postman for those instead.
Is my webhook URL or the payload data sent anywhere except my chosen destination?
No, the request goes directly from your browser to the URL you specify. This tool does not proxy, log, or store the request anywhere.
More free tools
Cron Expression Builder & Explainer
Turn any cron expression into plain English, or build one from scratch.
n8n Workflow JSON Validator
Paste your workflow JSON, catch orphaned connections and missing credentials before you import it.
n8n Expression Tester
Test {{$json.field}} style expressions against real sample data and see the exact output before pasting into n8n.