Free, no signup
Is my HTTP node actually firing?
Copy the URL below into your workflow, run it, and watch what arrives. You will see the method, the headers, the body, the source IP and the exact time it landed. No account, nothing to install, and the URL is already live.
Your test URL
expires in 60 minutes
https://silentfailapp.com/api/webhook-test/aYoM6D3kDFjq9gQZMgmKL8uMnK1J6R7bPaste it into an n8n HTTP Request node, a Make HTTP module, or Webhooks by Zapier, then run your workflow. Anything that arrives shows up below within a couple of seconds. Every method works, and the body is captured exactly as sent.
Waiting for a request
Nothing has arrived yet.
This page is watching. Run your workflow and the request will appear here on its own, no refresh needed. If nothing shows up, the request is not leaving your workflow, which is the answer you came for.
Once it fires, the harder question starts
This page proves the request leaves your workflow right now, while you are watching. Nobody is watching at 3am on a Sunday, and a workflow that quietly stops running sends nothing at all, so there is no error to notice. Silent Fail watches for the ping that does not arrive and emails you when it goes missing.
What this is doing
The URL points at a throwaway inbox that accepts any HTTP method and records what it receives. It is the same receiver Silent Fail uses for monitor pings, with the alerting taken out.
It lasts one hour. When it expires the inbox and everything it captured are deleted, not archived. Nothing is linked to you, because there is no account to link it to, and the URL is unguessable, so the only person who can read it is whoever holds the link.
Please do not point a loop at it or use it to relay traffic to anyone else. It is rate limited and capped, and the acceptable use rules in our terms apply here too.