webhook-subscriptions

Create webhook subscriptions that translate POST payloads into Hermes runs.

19|4|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/carterwayneskhizeine/hermes-agent-windows-R --skill webhook-subscriptions-carterwayneskhizeine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhook-subscriptions
Source: https://github.com/carterwayneskhizeine/hermes-agent-windows-R/tree/main/skills/devops/webhook-subscriptions
Command: npx skills add https://github.com/carterwayneskhizeine/hermes-agent-windows-R --skill webhook-subscriptions-carterwayneskhizeine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of manually starting Hermes runs when external systems (like GitHub or Stripe) have new events that should trigger automated actions.

Core Features & Use Cases

  • Create dynamic event-to-action subscriptions: Map incoming webhook payloads to Hermes prompt templates and deliver results to chat or other targets.
  • Use event filtering and prompt templating: Select which events to accept and inject nested payload fields using dot notation (for example, issue title, PR author, or sensor reading).
  • Support testing, direct delivery, and secure routing: Manage subscriptions with CLI commands, optionally bypass agent loops with --deliver-only, and authenticate requests with per-subscription HMAC secrets.

Quick Start

Configure the webhook platform with the setup wizard, start the gateway, then create a subscription that points GitHub (or another service) at the returned webhook URL using the secret you generated.

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 GitHub or Stripe webhooks?

Webhook subscriptions translate external POST payloads from GitHub or Stripe into Hermes prompt-triggered runs and deliveries. You configure a subscription that maps incoming webhook payloads to prompt templates, enabling event-driven agent automation for real-world events.

How do I authenticate incoming webhook requests with HMAC?

Webhook requests are authenticated using HMAC-SHA256 signature validation with a per-subscription shared secret. When you create a subscription, a secret is generated that the external service like GitHub or Stripe must include to sign outgoing payloads.

Can I inject specific fields from a webhook payload into an agent prompt?

Yes, event filtering and prompt templating allow you to select which events to accept and inject nested payload fields using dot notation. You can map specific payload data like issue titles, PR authors, or sensor readings directly into Hermes prompt templates.

Does webhook event automation support CI/CD pipeline notifications and IoT sensor triggers?

Yes, webhook subscriptions support CI/CD pipeline events, IoT sensor triggers, monitoring alerts, and payment notifications. The system maps these incoming webhook payloads to Hermes prompt templates and delivers results across multiple delivery adapters.

How do I set up and manage webhook subscriptions for event automation?

You use a setup wizard to configure the webhook platform and start the gateway, then create subscriptions via CLI commands. Subscriptions are persisted in a local JSON file and support runtime hot-reload of subscription routes on incoming requests.

Can I bypass the agent loop to directly deliver webhook payload data?

Yes, you can use the --deliver-only CLI option to bypass agent loops and directly deliver webhook payload data. This allows routing incoming webhook events straight to delivery targets without triggering a full Hermes prompt run.