Webhook Relay
PricingLogin
  • Introduction
  • Quick Start - Forwarding
  • Quick Start - Tunnels
  • 🛠️Installation
    • Relay CLI
      • Install
      • Auto-start
      • Run config.yaml reference
    • Containerized
      • Kubernetes Installation
      • Podman
      • Docker
      • Docker Compose
  • Products
    • 🛰️Webhook Forwarding
      • Glossary
      • WebSocket Server
      • Authentication
      • Custom Domains
    • ⚡Functions
      • Managing functions
      • Edit request/response
      • Working with JSON
      • 🦾Advanced
        • Working with time
        • Testing functions in CLI
        • Making HTTP Requests
        • Multipart Form Data
        • URLEncoded Form Data
        • GCP BigQuery
        • Sending Emails
        • JWT authentication
        • Base64, Hashes, Encryption
      • 🤖Integrating into CI/CD
    • 🔃Tunnels
      • Using tunnels
      • Custom Domains
      • Encryption (HTTPS)
      • Regions
  • 📝Examples
    • Intro to examples
    • Webhooks
      • Receiving webhooks on localhost
      • Receive webhooks inside your JavaScript app
      • Execute shell scripts on remote machines
    • Functions
      • Enrich webhooks from 3rd party APIs
      • Convert DockerHub webhook to Slack notification
      • Allowing only POST requests through
      • Manipulate webhook request body
    • Tunnels
      • Ingress for any Kubernetes environment
      • Demoing your website
    • 🏠Home Automation
      • Home Assistant
      • Node-RED
      • Raspberry Pi
  • Platform
    • CLI Basics
    • Using CLI Behind Proxy
    • Self-hosting Server
      • Server deployment
      • Client configuration
    • Security & Tech
Powered by GitBook
On this page
  • Buckets
  • Inputs
  • Outputs
  • Functions
  • Webhook Stats

Was this helpful?

  1. Products
  2. Webhook Forwarding

Glossary

Webhook Relay uses certain terms such as Buckets, Inputs, Outputs and Functions to enable webhook forwarding. This section explains them.

PreviousWebhook ForwardingNextWebSocket Server

Last updated 2 years ago

Was this helpful?

Buckets

Bucket is what holds the incoming and outgoing webhook configuration. To start webhook forwarding, you will need to create at least one bucket.

Inputs

Inputs are your public endpoints. This is where your applications or 3rd party services such as GitHub, Zapier, etc. need to send their webhooks.

There can be many inputs in a single bucket.

Outputs

Each output specifies a destination where webhooks can be forwarded to. Outputs can be either:

  • public - which are forwarded directly by Webhook Relay servers to the destination.

  • internal - which are forwarded through the agent (that you need to start in your environment).

There can be many outputs in a single bucket. Each received webhook will be forwarded to each output.

Functions

Functions are used to modify, filter or react to webhooks. They can be attached either to inputs, outputs or both.

You can use functions for:

  • Creating a dynamic response when Webhook Relay endpoint is hit (for example generating some code)

  • Transforming payload (received webhook from IFTTT can be sent to Zapier to trigger some flow)

  • Filter webhooks

  • Authenticate webhooks

  • etc.

Webhook Stats

You can view basic webhook counts for the last 7 days in your dashboard:

Here:

  • Received - webhooks that have been received on Webhook Relay but weren't forwarded. An example could be that the destination was internal but no clients were connected, hence nowhere to forward.

  • Success - received & successfully forwarded to the destination.

  • Failures - received & attempted to forward, however the server responded with an error. We attempt to deliver 5XX errors 5 times before giving up.

You can also view individual bucket logs:

You can filter based on date and status.

🛰️
Buckets hold both inputs endpoints and output destinations
Inputs are the public URLs where Webhook Relay is receiving HTTP requests
Output destinations instruct Webhook Relay where to send the webhooks
Webhook counts for the last week