Skip to main content
Microsoft
separator
https://catalogartifact.azureedge.net/publicartifacts/athinfosystems1641442221349.webhookd-991046bc-c095-4670-ad27-30c9a245f9ae/image1_webho216x216.png

webhookd

by ATH Infosystems

Version 1.22.0 + Free Support on Ubuntu 26.04

webhookd is an open-source, lightweight webhook server designed to execute shell scripts through HTTP requests. It provides a simple and efficient way to trigger scripts remotely using webhooks, making it suitable for automation, CI/CD workflows, system administration, event-driven tasks, and integration with external applications and services.

webhookd enables applications and services to invoke executable scripts through HTTP endpoints. It is designed to simplify automation by converting shell scripts into accessible webhooks without requiring a complex application framework. webhookd is suitable for developers, DevOps teams, system administrators, and organizations requiring a lightweight and flexible webhook execution platform.

Features of webhookd:

  • Provides a lightweight HTTP webhook server for executing scripts.
  • Enables shell scripts to be triggered through HTTP requests.
  • Supports simple and efficient event-driven automation workflows.
  • Can be integrated with CI/CD pipelines and external services.
  • Provides configurable webhook endpoints for executable scripts.
  • Offers a simple command-line interface for server configuration and management.
  • Supports automation tasks such as deployments, system administration, and service operations.
  • Can be run as a systemd service for automatic startup and service management.

webhookd Usage:

$ sudo su
$ apt update
$ cd /opt/webhookd

$ Verify webhookd Version:
$ webhookd --version

$ Check Installed Binary:
$ which webhookd

$ Check Webhookd Binary Version:
$ go version -m /usr/local/bin/webhookd | grep 'mod'

Disclaimer: webhookd is provided “as is” under its applicable open-source license. Users are responsible for configuring webhook endpoints, script permissions, authentication, network access, and security controls according to their organizational requirements. It is recommended to restrict access to webhook endpoints, use appropriate authentication and authorization mechanisms, validate incoming requests, secure communication with HTTPS where applicable, and carefully control the scripts that can be executed in production environments.

English (United States)
Your Privacy Choices Opt-Out Icon Your Privacy Choices
Consumer Health Privacy Sitemap Contact Us Privacy & Cookies Terms of Use About our ads Manage cookies