Test n8n webhooks on your own machine
Give a webhook provider one HTTPS callback address and reuse it when you restart your local n8n workflow.
5 simultaneous tunnels · 1 reserved fourth-level domain · 10 GB/month
Point a local proxy on port 8080 at the n8n test webhook path only. Use your reserved hostname below.
Set TUBU_TOKEN to your Tubu API key in this shell.
npx tubu-cli http 8080 \
--domain n8n-hook.tubu.devStart listening in n8n. Send a test event to your reserved hostname with the path from the Webhook node. The payload appears in your local workflow.
Reserve your callback address
Choose an available hostname such as n8n-hook.tubu.dev for this project. Keep the same address when you stop and restart the publisher.
Connect your test webhook
Run the publisher where it can reach n8n. Forward the test webhook path and keep the editor private. Use the path from your Webhook node in the provider’s callback URL.
See the event arrive
Start listening for a test event in n8n, then trigger one from the provider. Inspect the payload in the workflow before changing your integration.