webhook-subscriptions

Create and manage webhook subscriptions that trigger Hermes agent runs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and manage webhook subscriptions so external services can trigger Hermes agent runs by POSTing events to a URL.

Core Features & Use Cases

  • Dynamic subscriptions: Create, modify, and delete webhook routes that invoke Hermes actions based on incoming payloads from services like GitHub, GitLab, Stripe, CI/CD tools, or IoT sensors.
  • Secure delivery: Each subscription gets an auto-generated secret and validates signatures to protect against tampering.
  • Operational workflow: Manage subscriptions via the Hermes CLI, verify health, and forward payloads to configured skills for automated responses.

Quick Start

Create a webhook subscription and post a test payload to the generated URL to trigger an agent run.

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 automation run from an external webhook?

You can trigger an automation run by creating a webhook subscription that exposes a secure URL endpoint, allowing external services to POST event payloads and initiate the workflow automatically.

How do I secure webhook delivery from GitHub or Stripe events?

Securing webhook delivery involves validating event signatures using an auto-generated secret assigned to each subscription, which protects the endpoint against unauthorized tampering and malicious requests.

Can I use IoT sensor events to start an event-driven workflow?

Yes, IoT sensor events can start an event-driven workflow by POSTing payload data to the exposed subscription URL, which then forwards the data to configured skills for automated responses.

What's the best way to verify my webhook subscriptions are healthy?

The best way to verify webhook health is by running persistent configuration validation and health checks through the gateway CLI after creating or modifying your event subscription routes.