Use this service to:
- Forward webhooks to your local machine during development. For example Strip, Github, Slack integrations.
- Forward webhooks to internal network machines.
- Demo your websites from your development machine.
- Connect to low-traffic services through tunnels instead of getting public IP and domains (for example internal Grafana, Prometheus instances)
This services works by creating a reverse tunnels for one-way or bidirectional data transfer to internal services. Webhook Relay is designed to be easy-to-start-with and remain flexible enough for advanced use cases. Webhook Relay is perfectly capable of powering sophisticated use cases where performance and dynamic routing configuration is required.
Registration and agent installation (if needed for the use case) will take less than 5 minutes.
The easiest way to try out Web Relay is by using the
relay command client. Docker image is also available, you can view other deployment types here.
You can download the latest release from the link below:
Or if you have curl installed, use this command:curl -LO https://storage.googleapis.com/webhookrelay/downloads/relay-windows-amd64.exe
Add the binary in to your PATH.
In order to start using the service, you will need to create an account. If you already have an account, skip this section. Head to the registration page https://my.webhookrelay.com/register and register:
CREATE ACCOUNTfree plan available, no credit card required
Relay CLI needs credentials for your account. Once registered, generate a token and use token key and secret as a username and password for CLI authentication:
And then use it:
Another option is to set environment variables:
- Buckets - required to group your Inputs and Outputs.
- Inputs are public endpoint that start with /v1/webhooks/your-id
- Ouputs are destinations, where we forward webhooks. Outputs can be both public or internal.
At the core of Web Relay is a webhook delivery system that enables one-way HTTP request forwarding to the destination. Once webhook is accepted, it will be forwarded to all outputs listed in the bucket. To start forwarding:
We have already created our very first configuration for webhook forwarding! Any request that hits
https://my.webhookrelay.com/v1/webhooks/5e722a5e-f3d2-4hqec-9e9f-79f1158e4b10 endpoint will be forwarded to locally running application reachable on
http://localhost:8090/webhook address. Headers, method and body will be preserved.
All webhooks will appear in your bucket logs:
Another core feature of Web Relay are bidirectional tunnels that allow traffic to go both ways. If we want to connect to the same application reachable locally on http://localhost:8090 address, then use connect command:
That’s it! A new personal subdomain will be generated and you can access your locally running service through the public endpoint here. In this example the generated host is
Please note that custom subdomains are also available for paid plans.
We’ve briefly introduced the most basic features of Web Relay - the rest of this guide will cover them as well as other advanced features with much finer details.