- Use Case
- Log in →
- Security & Tech
- Webhook Forwarding
- Exec Commands
- WebSocket Server
- Functions guide
- Automating code updates
- HTTP Tunnels
- TLS Tunnels
- Global Infrastructure
- Ingress Controller (Tunnels)
- Webhook Relay Operator (Forwarding)
Internet of Things
- Home Automation
- Internet of Things (IoT)
- CLI commands
- Proxy Configuration
- Self-hosted deployment
- Client configuration
Relay CLI provides a variety of ways to configure request routing and also acts as an agent for request forwarding and tunneling. Main features:
- automatically configure bucket, input and output for webhook forwarding with
- automatically configure tunnel with
- manage buckets, inputs and outputs for one-way request forwarding
- manage tunnel subdomains, destinations and authentication details
- manage access keys and secrets
In order to start using your CLI, you first have to authenticate. Create your key & secret pair here: https://my.webhookrelay.com/tokens. Then, there are two ways to do it:
logincommand CLI will take advantage of native secure storage:
relay login -k token-key-here -s token-secret-here
- Environment variable option is very useful when automating things:
Forward command automatically creates configuration and starts one-way request forwarding:
relay forward --help
Here, to forward webhooks:
- -b –bucket: supply bucket name to reuse existing one. Useful when invoking forward command for the same destination.
- –no-agent: only configure bucket, input and output without starting an agent.
- -t –type: is an output, defaults to internal.
$ relay forward --bucket webhook-demo http://localhost:8090/webhook
Another forward mode is to execute commands on your machine, to do that, use:
- -b –bucket: supply bucket name to reuse existing one.
- –relayer: use ‘exec’ relayer type to execute commands.
- –command: command to execute, for example ‘python’, ‘bash’, ‘node’ and pretty much any other executable on your computer.
- –input-mode: by default only request body is passed through stdin into the executed command, use ‘json’ to retrieve body, headers, method, query and additional bucket/input metadata.
All additional arguments passed to the
forward command will be passed as arguments to the executed command:
relay forward --bucket my-bucket-name --relayer exec --command python my-script.py my-first-arg my-second-arg
Connect command automatically creates tunnel configuration and starts two-way request streaming:
$ relay connect -h
-r, --region string: is a tunnel region. Select your region based on your location (example: eu, us-west, au)
-d, --destination: is a destination to connect to.
--no-agent: only configures tunnel without starting an agent.
-p --password: is a password for the basic authentication.
-u --username: is a username for the basic authentication.
-t --token: is a token for the token authentication.
-s --subdomain: is an optional parameter for preferred subdomain. If not supplied - random subdomain will be generated.
$ relay connect https://localhost:9400
Buckets are used to group inputs and outputs for webhook relaying. Any request that hits an input in a bucket will be relayed to all outputs inside the same bucket.
To list all buckets:
relay bucket list
relay bucket create <new bucket name>
$ relay bucket create github
To update an existing bucket:
relay bucket update <bucket name or ID>
$ relay bucket update github -d "github webhooks"
To delete existing bucket:
$ relay bucket rm <bucket name or ID>
Note that this command will only delete buckets that have no Inputs or Outputs inside, but you can force
delete a bucket:
$ relay bucket rm -f <bucket name or ID>
$ relay bucket rm -f github
Inputs are your personal endpoints to receive webhooks.
To list all inputs:
relay input ls
To create an input:
$ relay input create -b <bucket> <name>
- -b –bucket: is a bucket name to use. Defaults to input name if not supplied.
- -d –description: is a description for the input.
To remove an input
$ relay input rm -b <bucket> <name or ID>
Outputs are destination where requests should be routed
To list all outputs:
relay output ls
To create an output:
$ relay output create -b <bucket> -d <destination> -t <type> <name>
-b --bucket: is a bucket name to use. Defaults to output name if not supplied.
-d --destination: is destination where request should be relayed.
-t --type: is output type. Available options: internal (default), public.
--header list: Set request override headers (key=value pairs) (default )
--description: is a description for the output.
To update an output:
$ relay output update <name> --bucket <bucket> --header <header key>=<header value> --destination <destination>
-b, --bucket: is a buucket name (required)
-d, --destination: is output destination - where request should be relayed
--header: allows to set request headers (key=value pairs) (default )
--id string: is an output ID
-t, --type string: is output type (available options: internal (default), public) (default ‘internal’) (default “internal”)
To remove an output:
$ relay output rm -b <bucket> <name or ID>
Tokens are used for API, CLI or webhookrelayd authentication.
To list all tokens:
relay token ls
To create a new token:
relay token create
Once token is generated - secret is already encrypted. Save it somewhere as we don’t store decrypted credentials.
If you lost your token’s secret - just remove it and create a new one.
To remove a token:
relay token rm <name or ID>
Tunnels are used to create bidirectional connections between public endpoint (ie: yourtunnel.webrelay.io) and local endpoint on your computer, private network or even remote website.
To list all tunnels:
relay tunnel ls
relay tunnel create [OPTIONS] [TUNNEL]
$ relay tunnel create --group webrelay-ingress hellonode
To update an existing tunnel:
relay tunnel update <tunnel name or ID> --crypto flexible
Usage example to enable public endpoint encryption:
$ relay tunnel update b8c5290a-3683-4774-a5d1-60028167d245 --crypto flexible
To delete existing tunnel:
$ relay tunnel rm <tunnel name or ID>
Ingresses are tunnels but with additional configuration to enable path based routing, tailored for Kubernetes ingresses. Tunnels that are of type ingress can be created using special group:
relay tunnel create --group webrelay-ingress hellonode
Then, these tunnels will be used by the ingress controller.
To view existing ingress type tunnels that already have path based routing rules:
$ relay ingress ls
$ relay ingress ls
Init command initializes ingress controller in your Kubernetes cluster. It prepares namespace, configures RBAC, provisions credentials for your account and creates a secret:
$ relay ingress init
There are additional options for this command (ie: if you don’t have RBAC enabled in your cluster, use
relay ing init -h
Reset command removes ingress controller from your cluster. Use this when you don’t want to use ingress controller anymore. However, dormant ingress controller barely uses any resources so it’s recommended to just remove your
ingress.yaml resources to disconnect tunnels.