I need to debug a webhook, how do I see what really arrives?
iPaaS tools show the incoming request, but locally or with a new integration you want an intermediate step showing all headers and body. Webhook.site, RequestBin and ngrok are the standard tools.
Try this first
- 1Quick inspection: create an endpoint at webhook.site. Paste the URL into the source, trigger an event, see payload + headers in your browser.
- 2Local testing against a dev environment: ngrok http 3000 gives you a public URL tunneling to localhost. Ready for Stripe CLI or similar local flows.
- 3Permanent debug layer: build a 'debug' branch in iPaaS that copies every incoming request to a logging step before production logic.
- 4Always compare headers: Content-Type, Signature, User-Agent. Many webhook bugs are in a missing or wrong header, not the body.
- 5Turn off debug once live. Webhook.site is readable by anyone with the URL, don't let production payloads land there.
When to bring us in
Webhook isn't arriving and the source is a SaaS where you can't see logs, we can sit in via a proxy layer.
See also
- n8n: self-host or cloud?Self-hosted is cheaper at volume and keeps data local. Cloud removes ops burden.
- Zapier or Make: which fits better?Zapier is straight-line; Make handles complex flows with routers and iterators for less money.
- Power Automate Cloud or Desktop: which to use?Cloud for SaaS integrations and triggers. Desktop for RPA against legacy Windows apps without APIs.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.