n8n

How to Automate Webhook.site Request Relay?

Receive public webhooks safely and pass them into your local n8n workflow with no port forwarding. Great for teams that need to capture external events while working behind a firewall or on a laptop. Useful for testing, demos, and controlled intake of inbound requests.

A schedule checks webhook.site every few seconds, using a stored token to read new requests. The flow reuses the token when it exists, or creates a new one and saves it in a key value store. It pulls the latest requests, merges them with the last processed time, and filters only new POST items. Each payload is sent as raw JSON to your local webhook URL. After relaying, it records the newest timestamp so the next run does not resend the same items.

Set a polling interval that fits your load and paste your local webhook URL into the configuration step. Expect faster testing cycles and fewer network headaches, since you do not need to expose your machine to the internet. This is ideal for QA, developers, and IT teams that want a simple way to receive external events during local development and early staging.

What are the key features?

  • Scheduled polling every 10 seconds using a Schedule Trigger
  • Token lifecycle with If logic to reuse an existing webhook.site token or create a new one
  • Key value storage to save the auth token and the last processed timestamp between runs
  • HTTP requests to fetch the latest webhook.site events for the stored token
  • Merge node to pair the last processed value with the newest request list
  • Code filter that selects only POST requests that arrived after the last processed time
  • Raw JSON relay to your local n8n webhook URL with the HTTP Request node
  • Automatic update of the last processed time after each successful relay

What are the benefits?

  • Reduce manual forwarding from hours of ad hoc testing to a few minutes of setup
  • Eliminate copy and paste steps by relaying payloads automatically to your local URL
  • Prevent duplicates by tracking the last processed time for each polling run
  • Connect public sources to a local environment without opening network ports
  • Speed up QA and developer testing cycles with reliable repeatable intake

How do you set it up?

  1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
  2. You'll need accounts with Webhook.site. See the Tools Required section above for links to create accounts with these services.
  3. Install the key value storage community node: In n8n go to Settings > Community Nodes > Install and enter @horka.tv/n8n-nodes-storage-kv.
  4. Open the Set node named Local Webhook Address and replace the example URL with the Webhook URL from your local workflow trigger. You can use a production or test URL from your local n8n instance.
  5. Double click the HTTP Request nodes Get Auth Token and Get Latest Requests. In the Credential to connect with field select None because webhook.site does not require authentication for these endpoints.
  6. Check the Schedule Trigger settings and choose a polling interval that fits your needs. The default is every 10 seconds.
  7. Confirm the key value nodes Store Auth Token and Store Last Processed are enabled so the token and timestamps persist between runs.
  8. Activate the workflow and let it run once. Then open Executions and copy the token value seen in the input to Get Latest Requests.
  9. Send a test event to webhook.site using curl with your token. For example post a small JSON body. After a few seconds check Executions and confirm that Unprocessed Requests contains your payload and that your local workflow received the same JSON.
  10. If no events arrive check the Code node Unprocessed Requests. It currently filters only POST items and expects JSON. Adjust the filter or content type if you need GET requests or raw payloads.
  11. If you see duplicated relays verify that Store Last Processed is updating. The Latest Update Time node should return the newest created time from the fetched events.

Tools Required

$24 / mo or $20 / mo billed annually to use n8n in the cloud. However, the local or self-hosted n8n Community Edition is free.

Webhook.site

Sign up

Free tier: $0, public API available; free URLs expire after 7 days and accept up to 100 requests

Similar Templates

Join Futurise to access 1,200+ automation templates

Get instant access to ready-made automation workflows for n8n, Make.com, AI agents, and more. Download, customise, and deploy in minutes.