WebHook is a lightweight and customizable tool written in Go that enables you to effortlessly create HTTP WebHook services. With WebHook, you can execute predefined commands and flexibly pass data from HTTP requests (including headers, body, and parameters) to your configured commands or programs. It also supports triggering hooks based on specific conditions.

For example, if you're using GitHub or Gitea, you can set up a hook with WebHook to automatically update your deployed program whenever you push changes to a specific branch of your project.

If you use Discord, Slack, or other messaging platforms, you can create an "Outgoing Webhook Integration" or "Slash Command" to run various commands on your server. You can then use the "Incoming Webhook Integration" feature of your messaging tool to report the execution results directly to you or your conversation channel.

The WebHook project has a straightforward goal: to do exactly what it's designed for.

• Receive requests
• Parse request headers, body, and parameters
• Verify if the hook's execution rules are met
• Pass specified parameters to the designated command via command-line arguments or environment variables

The specific commands - whether processing data, storing information, or controlling devices - are entirely up to you. WebHook's role is to accept and execute instructions at the appropriate time.

Let's explore how to download the executable program and quickly set it up to connect various applications.

WebHook offers pre-built executable programs for various operating systems and architectures. You can download the version suitable for your platform from the Releases page on GitHub.

You can use any of the following commands to download the automatically built executable program image:

docker pull soulteary/webhook:latest
docker pull soulteary/webhook:3.6.0

For an extended version of the image that includes debugging tools, use:

docker pull soulteary/webhook:extend-3.6.0

You can then build and refine the runtime environment required for your commands based on this image.

We recommend reading the complete documentation to fully understand the program's capabilities. English Documentation, Chinese Documentation

Let's define some hooks for webhook to provide HTTP services.

webhook supports both JSON and YAML configuration files. We'll start with JSON configuration.

Create an empty file named hooks.json. This file will contain an array of hooks that webhook will start as HTTP services. For detailed information on hook properties and usage, please refer to the Hook Definition page.

Here's a simple hook named redeploy-webhook that runs a redeployment script located at /var/scripts/redeploy.sh:

[
  {
    "id": "redeploy-webhook",
    "execute-command": "/var/scripts/redeploy.sh",
    "command-working-directory": "/var/webhook"
  }
]

If you prefer YAML, the equivalent hooks.yaml file would look like this:

- id: redeploy-webhook
  execute-command: "/var/scripts/redeploy.sh"
  command-working-directory: "/var/webhook"

To run webhook, use the following command:

$ /path/to/webhook -hooks hooks.json -verbose

The program will start on the default port 9000 and provide a publicly accessible HTTP service address:

http://yourserver:9000/hooks/redeploy-webhook

To learn how to customize IP, port, and other settings when starting webhook, check out the webhook parameters documentation.

Any HTTP GET or POST request to the service address will trigger the redeploy script.

To enhance security and prevent unauthorized access, you can use the "trigger-rule" property to specify exact conditions for hook triggering. For a detailed list of available rules and their usage, please refer to Hook Rules.

webhook offers limited parsing support for form data, including both values and files. For more details on how form data is handled, please refer to the Form Data documentation.

webhook supports parsing the hook configuration file as a Go template when using the -template command line argument. For more information on template usage, see Templates.

While webhook serves using HTTP by default, we recommend using a reverse proxy or a service like Traefik to provide HTTPS service for enhanced security.

To set CORS headers, use the -header name=value flag when starting webhook. This will ensure the appropriate CORS headers are returned with each response.

Explore various creative uses of WebHook in our Hook Examples documentation.

We decided to fork this open-source software for two main reasons:

1. To address security issues and outdated dependencies in the original version.
2. To incorporate community-contributed features and improvements that were not merged into the original repository.

Our goal is to make WebHook more reliable, secure, and user-friendly, including improved documentation for our Chinese users.