webhook-subscriptions

Create and manage webhook subscriptions that trigger Hermes agent runs.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/attentiondotnet/hermes-agent --skill webhook-subscriptions-attentiondotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhook-subscriptions
Source: https://github.com/attentiondotnet/hermes-agent/tree/main/skills/devops/webhook-subscriptions
Command: npx skills add https://github.com/attentiondotnet/hermes-agent --skill webhook-subscriptions-attentiondotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create dynamic webhook subscriptions so external services (GitHub, GitLab, Stripe, CI/CD, IoT sensors, monitoring tools) can trigger Hermes agent runs by POSTing events to a URL.

Core Features & Use Cases

  • Manage webhook subscriptions via the hermes webhook CLI with per-subscription secrets and event-driven triggers.
  • Automatically route events to configured delivery targets (Telegram, Discord, GitHub comments, etc.) and persist subscriptions for cross-session reliability.
  • Support common integration patterns: generating webhook URLs, validating signatures, and testing subscriptions locally.

Quick Start

Enable the webhook platform if required and create your first subscription with the hermes webhook subscribe command.

Frequently Asked Questions about webhook-subscriptions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trigger automated agent runs from external services like GitHub or Stripe?

Webhook subscriptions enable external services like GitHub or Stripe to trigger automated agent runs by POSTing event data to a dynamically generated URL. This allows event-driven activations without manual polling or continuous execution.

How do I create and manage webhook subscriptions for event-driven automation?

You can create and manage webhook subscriptions using the hermes webhook CLI. The command-line interface generates unique webhook URLs and HMAC secrets, persisting configuration locally under ~/.hermes/webhook_subscriptions.json for cross-session reliability.

Do I need a webhook gateway to route events to delivery targets like Discord?

A configured webhook gateway is required to route incoming events to delivery targets like Discord, Telegram, or GitHub comments. The gateway validates HMAC signatures and automatically directs the event payloads to the configured notification channels.

Can I use webhook subscriptions with CI/CD pipelines and IoT sensor events?

Webhook subscriptions support integration with CI/CD pipelines, IoT sensors, and monitoring tools. Any external system capable of sending HTTP POST requests to a webhook URL can trigger an event-driven activation through the generated endpoint.

How are webhook signatures validated for secure event-driven triggers?

Webhook subscriptions secure event-driven triggers using HMAC secrets generated per subscription. The external service signs the event payload with this secret, allowing the gateway to validate the signature and ensure the incoming request is authentic.