webhook-subscriptions

Create dynamic webhook subscriptions that trigger Hermes agent runs from JSON event POSTs.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/mattei2005/mgs-agent --skill webhook-subscriptions-mattei2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhook-subscriptions
Source: https://github.com/mattei2005/mgs-agent/tree/main/profiles/atena-skills/devops/webhook-subscriptions
Command: npx skills add https://github.com/mattei2005/mgs-agent --skill webhook-subscriptions-mattei2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Webhook-subscriptions eliminates the manual coordination required to react to external events by automatically turning incoming POST events into Hermes agent runs.

Core Features & Use Cases

  • Event-driven subscriptions: Create named webhook routes that listen for specified event types and map their payloads into agent prompts.
  • Flexible prompt templating: Use dot-notation placeholders to extract nested fields from JSON payloads, or fall back to using the full payload when no prompt is provided.
  • Optional direct delivery: Forward rendered messages straight to a delivery adapter (zero agent/LLM cost) using deliver-only for simple notifications and relay workflows.

Quick Start

First ensure the Hermes webhook platform is enabled, then create a subscription for your event source by asking: "Create a webhook subscription named ci-builds that listens to pipeline events and sends the rendered build status and commit message to my Discord."

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 incoming webhook events?

Webhook subscriptions secure inbound requests by validating HMAC secrets, ensuring that only authorized external systems can trigger your agent runs. This cryptographic verification prevents unauthorized or tampered event delivery.

How do I extract specific fields from a JSON payload to use in my agent prompt?

You extract specific fields by using dot-notation placeholders in your prompt templates to pull nested values from the JSON payload. If no prompt template is provided, the system defaults to passing the full payload directly to the agent.

Can I forward webhook events as simple notifications without invoking an LLM?

Yes, you can forward events without an LLM by using the deliver-only option to route rendered messages straight to a delivery adapter. This enables zero agent cost notifications and relay workflows for simple alerts.

Does this webhook integration work with CI/CD pipelines and GitHub event payloads?

Yes, the webhook gateway supports integrating with systems like GitHub, GitLab, Stripe, CI/CD pipelines, and IoT sensors. It processes their emitted JSON payloads to trigger your specified agent workflows automatically.

How are inbound webhook requests secured against unauthorized triggers?

Inbound webhook requests are secured using HMAC secrets to validate the source of the event POSTs. This ensures only authenticated external systems can trigger your Hermes agent runs.

What is required to set up a named webhook route for pipeline events?

Setting up a named webhook route requires enabling the Hermes webhook gateway, defining event filters, and creating prompt templates with dot-notation payload fields. You must also configure HMAC secrets to secure the inbound requests.