webhook-subscriptions

Create secure webhook subscriptions that trigger Hermes agent runs from external events.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of wiring external events into Hermes by letting you create secure webhook subscriptions that trigger agent runs automatically.

Core Features & Use Cases

  • Event-Driven Automation: Subscribe to events from GitHub, GitLab, Stripe, CI/CD tools, IoT sensors, and monitoring systems.
  • Flexible Prompt Routing: Map incoming payload fields into prompt templates so each event produces a tailored agent response.
  • Delivery and Notification Targets: Send results to Telegram, Discord, GitHub comments, Slack, or direct delivery flows for zero-LLM notifications.
  • Security and Reliability: Use HMAC signing, event filters, idempotent delivery behavior, and subscription persistence for safer production use.

Quick Start

Ask Hermes to create a webhook subscription for your chosen event source and delivery target, with a custom prompt and the correct secret for secure event forwarding.

Frequently Asked Questions about webhook-subscriptions

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

FAQPage Schema
How do I trigger an agent run automatically from a GitHub or Stripe webhook?

Webhook subscriptions trigger agent runs automatically by creating secure endpoints that receive posted events from GitHub, Stripe, or CI/CD systems. You configure a delivery target and prompt template, and the event payload maps into the prompt to produce a tailored response.

Can I filter webhook events so my agent only runs for specific payload conditions?

Event filtering is supported natively in webhook subscriptions, allowing you to specify conditions so agent runs only trigger for specific payload fields. This prevents unnecessary executions and ensures your Hermes agent responds only to relevant events.

Does this webhook integration support HMAC signature validation for secure event forwarding?

HMAC signature validation is a required security feature for webhook subscriptions, ensuring that incoming events from external services like GitLab or IoT sensors are securely authenticated before triggering any agent actions.

How do I route webhook event results to Telegram, Discord, or Slack notifications?

Delivery routing in webhook subscriptions sends results to notification targets including Telegram, Discord, Slack, or GitHub comments. You map incoming payload fields into prompt templates and direct the output to your chosen chat or agent target.

What is the best way to map incoming webhook payload fields into an agent prompt template?

Prompt templating from payload fields is a core feature of webhook subscriptions, letting you extract data from incoming events and inject it into custom prompts. This ensures each event from services like Stripe or CI/CD tools produces a tailored agent response.

Are webhook deliveries idempotent to prevent duplicate agent runs from retried events?

Webhook subscriptions include idempotent delivery behavior and subscription persistence to prevent duplicate agent runs when external services retry event posts. This ensures safer production use for critical event-driven automation workflows.