(TO THE GOD OF ABRAHAM, ISAAC AND JACOB. I DEDICATE THIS WORK TO YOU MAY YOU BLESS IT AND MAY IT BLESS THOSE YOU USE IT, MORESO MAY THEY KNOW YOU BY NAME, REPENT AND BE LED TO YOUR WILL AND KINGDOM.) Our Father who is in the heavens, let Your Name be set-apart,let Your reign come, let Your desire be done on earth as it is in heaven. Give us today our daily bread. And forgive us our debts, as we for- give our debtors. And do not lead us into trial, but deliver us from the wicked one because Yours is the reign and the power and the esteem, forever. Amen.
ThunderHooks - Webhook Testing & Debugging Tool | Test Webhooks Locally

Relay Rules

Forward webhooks to localhost or other URLs automatically

What are relay rules?

A relay rule automatically forwards captured webhooks to another URL. When a request hits your ThunderHooks endpoint, the relay sends a copy to your target — your local dev server, a staging environment, or another service.

This replaces the need for tools like ngrok when testing webhooks locally.

Setting up a relay

  1. Go to your endpoint and click Relays
  2. Click New Relay Rule
  3. Enter a name and the target URL (e.g. http://localhost:3000/webhooks/stripe)
  4. Enable the rule

Now every webhook that hits your ThunderHooks endpoint also gets forwarded to your local server.

Target URL

The relay sends the original request body and headers to your target URL using the same HTTP method. Your target receives essentially the same request the webhook provider sent.

For local development, you'll need your machine to be reachable. The relay forwards from ThunderHooks servers, so localhost URLs won't work directly — use your machine's public IP or a tunnel.

Retries

Relay rules support automatic retries if the target returns an error or is unreachable:

  • Max retries — how many times to retry (default: 3)
  • Backoff — delay between retries in milliseconds

Filtering

You can add filter conditions to only relay certain requests. Filters match against request headers, method, or body content.

Execution history

Each relay rule tracks its forwarding history. Click into a rule to see:

  • Target URL and status (success/failure)
  • Response status code from your server
  • Duration and retry attempts
  • Error messages if something went wrong

Credits

Each relay execution consumes 1 credit from your account balance.