webhook-subscriptions

Create and manage webhook subscriptions that trigger Hermes agent runs.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/JKhyro/HERMES-AGENT --skill webhook-subscriptions-jkhyro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhook-subscriptions
Source: https://github.com/JKhyro/HERMES-AGENT/tree/main/skills/devops/webhook-subscriptions
Command: npx skills add https://github.com/JKhyro/HERMES-AGENT --skill webhook-subscriptions-jkhyro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual polling and copy-paste workflow by turning incoming events from external services into automatic Hermes agent runs.

Core Features & Use Cases

  • Event-Driven Activation: Create webhook subscriptions that fire when GitHub, GitLab, Stripe, CI systems, monitoring tools, or IoT devices send matching events.
  • Secure Delivery: Use HMAC protection, route validation, and persistent subscription storage to keep webhook-triggered runs reliable and controlled.
  • Flexible Response Routing: Deliver agent results to destinations such as Telegram, Discord, GitHub comments, or the originating channel.
  • Use Case: A team can route new issue events into a triage prompt so Hermes summarizes the issue, suggests next steps, and posts the response to a chat channel.

Quick Start

Ask the skill to create a webhook subscription for a chosen event source, prompt template, and delivery target.

Frequently Asked Questions about webhook-subscriptions

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

FAQPage Schema
How do I trigger agent runs automatically from GitHub or Stripe webhooks?

Webhook subscriptions trigger agent runs automatically by receiving incoming POST events from external services like GitHub or Stripe, validating the payload, and executing a predefined prompt template without manual polling.

How does HMAC signature validation secure incoming webhook events?

HMAC signature validation secures incoming webhook events by cryptographically verifying that the payload originates from a trusted source, preventing unauthorized requests from triggering agent runs or injecting malicious data.

Can I route automated agent responses to Telegram or Discord after a webhook fires?

Configurable delivery targets route automated agent responses to Telegram, Discord, GitHub comments, or the originating channel, ensuring event processing results reach the correct team communication workflow.

What is the best way to stop manual polling for CI/CD and monitoring event updates?

Event-driven activation through persistent webhook subscriptions eliminates manual polling by automatically firing agent runs when CI/CD pipelines, monitoring tools, or IoT devices send matching event updates.

Does this webhook subscription approach work with GitLab and IoT device payloads?

Yes, the webhook subscription mechanism applies to GitLab, Stripe, CI/CD, monitoring workflows, and IoT devices, using payload templating to process diverse incoming POST events into actionable agent prompts.

Do I need persistent storage to manage webhook subscriptions for external events?

Persistent subscription storage is required to manage webhook subscriptions, keeping event routing configurations, delivery targets, and prompt templates reliably available for incoming external events.