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.