webhook-subscriptions

Route external POST events to Hermes agent runs via CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Webhook subscriptions enable external services to trigger Hermes agent runs or push notifications to chats, reducing manual task switching and latency.

Core Features & Use Cases

  • Event-driven triggers: Subscribe external services (GitHub, Stripe, CI/CD, IoT sensors) to POST events to Hermes and activate agent runs.
  • Flexible delivery: Route events to channels like Telegram, Discord, or other adapters; supports zero-LLM-cost direct delivery when appropriate.
  • Security & persistence: Each subscription can use a generated or user-provided HMAC secret; subscriptions are persisted locally for reliable recovery and auditing.

Quick Start

Configure the webhook gateway, create a subscription, and verify delivery works.

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 workflow from external webhooks and alerts?

Triggering an agent workflow from external webhooks automates the routing of external POST events to Hermes agent runs. It enables event-driven workflows for services like GitHub, Stripe, or CI/CD pipelines without manual task switching.

Can I use HMAC secrets to secure webhook subscriptions for GitHub or Stripe events?

HMAC secrets secure webhook subscriptions by allowing you to generate or provide a unique secret per subscription. This validates incoming POST events from GitHub, Stripe, or other services before triggering an agent run.

How does event-driven automation route external POST events to chat channels?

Event-driven automation routes external POST events to chat channels like Telegram or Discord for flexible delivery. It supports zero-LLM-cost direct delivery when appropriate, reducing latency and manual task switching.

Do I need a CLI to configure webhook subscriptions and manage local persistence?

A CLI is needed to configure webhook subscriptions, implement health checks, and manage local persistence. Subscription data is stored locally in the ~/.mercury directory to ensure reliable recovery and auditing.

What external services can I integrate with using webhook subscriptions for automation?

Webhook subscriptions support integrations with GitHub, Stripe, CI/CD pipelines, and IoT sensors. These external services POST events to Hermes, activating agent workflows through a secure, event-driven trigger mechanism.

Are there limitations when using webhook subscriptions for direct chat delivery?

Limitations of webhook subscriptions include relying on local persistence in ~/.mercury for recovery rather than cloud storage. Direct delivery to chat channels is supported but depends on configured adapters like Telegram or Discord.