The problem
Debugging webhooks means adding logging, redeploying and guessing what the provider actually sent.
What you get
Capture Inbox with forwarding target, signature verification and replay template
Public, unique capture endpoints that collect inbound requests, manage retention and parsing settings. Fields: description, public url, provider type, retention (days). Open one to see and add its forwarding target, signature verification, replay template.
Capture URLs
Create unique public endpoints; every request is stored with method, headers, source IP and the exact raw body.
Inspect payloads
Browse captured requests, read headers (credentials masked) and pretty-printed JSON.
Byte-exact replay
Re-send a request to a public URL with the original bytes and headers. Providers that sign a timestamp still enforce their window (Stripe: 5 minutes), so replay soon after capture or relax tolerance in test.
Edit before replay
Change a payload deliberately and see the response status, body and latency.
Test payload simulator
Fire a realistic sample event without exposing anything to the internet.
Guardrails
Per-endpoint rate limits, size limits, retention windows and private-network blocking.
Hosted, not local
Replays reach public staging or production URLs. To hit localhost, expose it with a tunnel (e.g. ngrok or Cloudflare Tunnel).
CSV / Excel export
Download any of your tables as a CSV that opens cleanly in Excel or Google Sheets.
PDF reports
Export a list, or one record with all of its child records and history, as a PDF report for audits, clients or your files.
Webhooks for Zapier & Make
Every create, change and delete is sent as signed JSON to Zapier, Make, n8n or any URL you add in Settings.
How it works
- 1
Create a capture endpoint and copy its URL
a unique public capture URL exists
- 2
Send a webhook to the capture URL
the request is persisted with headers, body and source IP
- 3
Inspect the captured event (or send a test payload)
headers and payload render; secrets are masked
- 4
Edit the payload and replay it to a target URL
the response status, body and latency are logged