Latenode
HTTP Request

Route incoming webhooks to a local server without a proxy

This automation template allows developers and infrastructure teams to easily receive and securely forward incoming webhooks from external services to a local server or private endpoint, without requiring a remote proxy.

It sets up a local webhook address, retrieves and processes new webhook requests, and stores the latest request time for subsequent runs. This is particularly useful for quickly testing integrations during development without exposing a public-facing server. The automation utilizes common n8n nodes like the Schedule Trigger, HTTP Request, Code, and Key-Value Storage to handle the webhook ingestion, processing, and local delivery in a seamless manner.

Updated Apr 6, 2026Est. run: 26sEst. cost: $0.0703
How Latenode estimates time and cost

Latenode bills workflow runs in credits: 1 credit = 30 seconds of processing. Minimum charge per run depends on your plan. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.

Full pricing — how credits work →
Development & API

Workflow preview

What this template does

  • Sets up a local webhook address to receive incoming requests from external services
  • Retrieves and processes new webhook requests in a secure and reliable manner
  • Stores the latest request time to track and handle subsequent runs efficiently
  • Forwards the processed webhook data to a local server or private endpoint
  • Enables developers to quickly test integrations during development without exposing a public-facing server

How it works

1
Trigger

Schedule Trigger

This workflow is triggered by a schedule that runs every 10 seconds. This ensures the workflow checks for and processes any new incoming webhook requests on a regular interval.

2
Action

Get Latest Requests

The workflow fetches the latest unprocessed webhook requests from the locally generated webhook address, which was previously stored as a variable.

3
Logic

Process Requests

The retrieved webhook requests are then filtered, transformed, and prepared for forwarding to the local server or private endpoint. This step ensures the requests are in the correct format and contain any necessary data or metadata.

4
Action

Forward Requests

The processed webhook requests are then forwarded to the local server or private endpoint using an HTTP POST request. This allows the external service's data to be securely delivered to the internal system without exposing a public-facing server.

5
Action

Update Last Processed

After successfully forwarding the requests, the timestamp of the latest processed request is stored as a variable. This ensures that only new, unprocessed requests are fetched and forwarded in subsequent runs of the workflow.

Setup guide

1

Add Webhook Integration

1. In the Latenode builder, add a Webhook node. 2. Configure the Webhook node settings: - Set the Webhook URL to the desired local endpoint (e.g. `/webhook`). - Enable the 'Catch All' option to receive all incoming webhooks.

2

Add HTTP Request Node

1. In the Latenode builder, add an HTTP Request node. 2. Configure the HTTP Request node settings: - Set the Request URL to the local endpoint (e.g. `http://localhost:5678/webhook`). - Select the 'POST' method. - Map the incoming webhook data to the request body.

3

Add Key-Value Storage Node

1. In the Latenode builder, add a Key-Value Storage node. 2. Configure the Key-Value Storage node settings: - Set the 'Key' to 'last_processed'. - Use the 'Latest Update Time' output from the HTTP Request node to store the last processed webhook timestamp.

4

Add Code Node

1. In the Latenode builder, add a Code node. 2. In the Code node settings, add custom JavaScript logic to: - Generate a unique identifier for the incoming webhook (e.g. using `uuidv4()`). - Forward the webhook data to the local server or private endpoint.

5

Connect the Nodes

1. In the Latenode builder, connect the nodes in the following order: - Webhook node -> HTTP Request node - HTTP Request node -> Key-Value Storage node - HTTP Request node -> Code node

Requirements

A workspace in the n8n automation platform
Access to the HTTP Request and Code nodes within the n8n workspace
Access to the Key-Value Storage node within the n8n workspace
Ability to configure incoming webhook URLs and securely forward them to a local server or private endpoint

FAQ

Common questions about this template

Each run uses credits on your Latenode plan. We charge for processing time (1 credit = 30 seconds). Your actual cost depends on your plan and how long the run takes. See pricing plans for plans and how credits work.
Contact support →

More templates

You might also like

Browse all templates →
Development & API

Automatically trigger webhooks from new Gravity Forms entries

This automation template allows users to trigger a custom webhook URL whenever a new entry is submitted through a Gravity Forms integration. The automation is designed for developers, API users, and infrastructure teams who need to build custom integrations and workflows that respond to data from Gravity Forms. It involves connecting Gravity Forms to a webhook endpoint, which could then forward the form data to another system or service for further processing. This enables users to build custom backend logic and integrations around their Gravity Forms data without having to manually monitor the form or build a custom integration from scratch.

26s$0.0703
Development & API

Automatically create Knack records from external data webhooks

This automation allows users to automatically receive data from an external source via a webhook and use that information to create a new record in a specified Knack application. The automation is designed for developers, IT professionals, and others who need to integrate external data sources with their internal applications. It involves setting up a webhook to receive data from an external source, processing that data, and then creating a new record in a Knack application based on the received information. The automation helps streamline data integration and reduces the need for manual data entry, improving efficiency and productivity.

26s$0.0703
Development & API

Automatically generate OpsGenie alerts from incoming webhooks

This automation template monitors incoming webhooks for specific events, such as infrastructure changes or application errors, and automatically generates corresponding alerts in the OpsGenie incident management platform. This allows the relevant development, API, and infrastructure teams to be notified promptly so they can investigate and resolve issues. The automation streamlines the incident response process, improving operational efficiency and reducing the time to resolution for critical events.

26s$0.0703