webhook-subscriptions

Create webhook subscriptions that trigger agent runs from external service events.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? External services like GitHub, Stripe, and CI/CD pipelines emit events that normally require manual checking; this Skill lets those services trigger Hermes agent runs automatically by POSTing events to a webhook URL. ## Core Features & Use Cases - Dynamic Subscriptions: Create, list, test, and remove webhook subscriptions via the hermes webhook CLI with HMAC-SHA256 signature validation. - Prompt Templates: Use {dot.notation} placeholders to inject nested payload fields (issue titles, PR authors, payment amounts) into agent prompts. - Direct Delivery Mode: Use --deliver-only to push rendered messages straight to Telegram, Discord, or Slack with no LLM round trip. - Use Case: Subscribe to GitHub issues events so every new issue is triaged by an agent and the result is delivered to a Telegram chat. ## Quick Start Set up a webhook subscription named github-issues that triggers an agent to triage new GitHub issues and delivers the result to my Telegram chat.

Frequently Asked Questions about webhook-subscriptions

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

FAQPage Schema
How do I create a webhook subscription to trigger an agent from GitHub events?▼

Run `hermes webhook subscribe` with a name, an `--events` filter like "issues", a `--prompt` template using payload fields, and a `--deliver` target. The command returns a webhook URL and HMAC secret to paste into GitHub's webhook settings.

How do I enable the webhook platform before creating subscriptions?▼

Run `hermes gateway setup` and follow the prompts, or manually set `platforms.webhook.enabled: true` with a port and secret in `~/.hermes/config.yaml`. Then start the gateway with `hermes gateway run` and verify with `curl http://localhost:8644/health`.

Can webhook notifications be delivered without running an LLM agent?▼

Yes, add `--deliver-only` to the subscribe command so the rendered prompt template is sent directly to the delivery target with no agent loop. The target must be a real adapter like telegram or discord; `--deliver log` is rejected.

Why is my webhook subscription not triggering on incoming events?▼

Check that the gateway is running, the health endpoint returns ok, and the service's secret matches the one from `hermes webhook list`. Also verify the `--events` filter matches the sent event type and use `hermes webhook test <name>` to validate the route.

How are webhook payloads secured against unauthorized requests?▼

Each subscription gets an auto-generated HMAC-SHA256 secret, and the adapter validates signatures on every incoming POST. GitHub sends `X-Hub-Signature-256` and GitLab sends `X-Gitlab-Token` for verification.