Latenode

Route incoming webhooks to a local server without a proxy

This template gives senders a Latenode webhook URL. When a payload arrives, JavaScript can reshape it, then an HTTP request POSTs it to the local or private URL you set.

Put that destination URL on the HTTP request step, with any auth header the endpoint needs. Use it to reach a server on your network without standing up a separate reverse proxy.

Updated Sep 16, 2026Est. run: 13sEst. cost: $0.0008
How Latenode estimates time and cost

Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. 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 CPU seconds work →

Workflow preview

What this template does

  • Receives incoming webhooks on a Latenode URL
  • Forwards each payload to the private HTTP URL you set
  • Shapes the body in JavaScript before the POST
  • Keeps destination auth on the HTTP request step

How it works

1
Trigger

Receive the webhook

A webhook starts the scenario when an external service posts a payload to the Latenode URL.

2
Logic

Shape the payload

JavaScript keeps the fields your private endpoint expects and drops anything you do not want to forward.

3
Action

POST to your private URL

An HTTP request sends that JSON to the local or private URL you set. Put any auth header on that same step.

Setup guide

1

Add the webhook

Add a webhook trigger and copy its URL. Point the sending system at that URL so Latenode receives each payload.

2

Set the private destination

Add an HTTP request step. Paste the local or private HTTPS URL that should receive the POST. Put a bearer token or other header on that same step if the endpoint requires it.

3

Map and test

In JavaScript, return the JSON body the destination expects. POST a test payload to the Latenode webhook and confirm it arrives at your private endpoint. If the source only offers a poll URL, run on a schedule, HTTP GET new payloads, and POST each one to that same private URL.

Requirements

A sender that can POST JSON to a Latenode webhook, or an inbox URL you can poll
A local or private HTTP URL that accepts the forwarded POST
Any auth header that private endpoint expects, stored on the HTTP request step

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.