What is webhook forwarding?
Webhook forwarding is the practice of receiving an inbound webhook at one endpoint and passing it on to another URL. A webhook forwarder — also called a webhook relay or webhook proxy — decouples the service that sends events from the services that consume them. You give providers one stable URL and change where events go without ever touching their configuration again.
NodeTrigger is a webhook forwarding service built for reliability. Beyond plain relaying, it verifies sources, applies filter rules, and can fan out to multiple destinations — the full webhook router pipeline.
Receive one webhook, filter it, and forward it anywhere. Change destinations from a dashboard instead of re-configuring every upstream provider.
Why forward webhooks through NodeTrigger?
- One stable inbound URL. Providers never need to know your real backend address, which can change freely behind the forwarder.
- Durable by default. Every webhook is written to a fail-safe JSON log before forwarding, so a crash mid-delivery loses nothing. See Fail-Safe Storage.
- Automatic retries. Up to five attempts with exponential backoff when a destination is briefly down. See Retries & Delivery.
- Replay any event. Re-forward a past webhook through current rules with one click. See Flow Log & Replay.
- Secure forwarding. Stripe/Shopify signatures verified; SSRF-guarded delivery; auth and cookie headers stripped. See Security.
Forwarding vs. filtering vs. fan-out
These three capabilities stack:
- Forward — pass an inbound webhook on to a destination URL. The baseline.
- Filter — forward only when the payload matches your conditions, so downstream tools stay quiet. See the filtering guide.
- Fan out — forward the same event to several destinations at once. See multiple destinations.
You can use forwarding on its own, or layer filtering and fan-out on top — all configured on the same visual canvas, documented in the Routes guide.
Frequently asked questions
What is the difference between a webhook forwarder and a webhook proxy?
The terms are used interchangeably. Both receive an inbound webhook and pass it to another URL. NodeTrigger adds verification, filtering, transformation, and fan-out.
Does forwarding add reliability, or just relay?
It adds reliability: durable storage before delivery, automatic retries with backoff, and one-click replay of any past event.
Can I change the destination without touching the provider?
Yes — that is the point. The provider keeps posting to one NodeTrigger URL while you edit destinations in the dashboard.
Which providers can I forward from?
Any service that sends HTTP webhooks. Stripe and Shopify get native signature verification.
Forward your webhooks, reliably
One inbound URL, forwarded anywhere — with retries, durable storage, and replay behind every event.