Debug Zapier, Make, and n8n webhooks with real payloads.
Automation platforms are generous with triggers and quiet about what they actually send. Put a SignalBin endpoint in the middle and the payload stops being a mystery: you get the exact body, the exact headers, and a record you can point at when a scenario misfires.
Exact request bodiesNo tunnel to keep aliveHistory you can filter
Workflow
How the debugging loop goes.
01
Give the automation a URLCreate an endpoint and paste its URL into the Zapier action, Make module, or n8n HTTP request node you are building.
02
Run the scenario onceExecute the automation for real. SignalBin captures the request whether it is JSON, form-encoded, or a multipart upload with files attached.
03
Build against the real shapeRead the stored body to see the field names and types the platform actually emits, then write your handler against that instead of against the documentation screenshot.
04
Chain it onwardAdd your service as a destination once the shape is settled, and the same endpoint keeps capturing while it forwards.
Details
Worth knowing before you wire it up.
Attachments are keptMultipart uploads are stored as downloadable files alongside the request, so a scenario that posts a generated PDF or CSV is debuggable too.
Any method, any content typeEndpoints accept whatever the platform sends and record the detected body type, which is often the fastest way to spot a wrong content-type header.
One endpoint per scenarioSeparate endpoints per automation keep history readable when half a dozen scenarios are firing into the same workspace.
FAQ
Common questions.
Can SignalBin return a specific response to the automation?
Yes. Per-endpoint mock rules let you choose the status code and body an incoming request gets back, which is how you exercise the failure branch of a scenario.
Will it capture form-encoded posts?
Yes. Form-encoded and multipart requests are captured the same way as JSON, with attached files stored as downloads.
Do I need to keep a laptop online?
No. The receiving URL is hosted, so the automation can fire at 3am and the capture is waiting for you.
Start with one endpoint.
Send a request, open the payload, and see exactly what your provider delivered.