webhook-subscriptions

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

Updated May 13, 2026
One-click install
npx skills add https://github.com/superfhp/lumi-agent-body --skill webhook-subscriptions-superfhp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: webhook-subscriptions
Source: https://github.com/superfhp/lumi-agent-body/tree/main/skills/devops/webhook-subscriptions
Command: npx skills add https://github.com/superfhp/lumi-agent-body --skill webhook-subscriptions-superfhp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? External services like GitHub, Stripe, and CI/CD pipelines emit events that require manual monitoring; this Skill lets those services trigger automated agent runs 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 auto-generated HMAC-SHA256 secrets. - 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 without an LLM round trip. - Use Case: Subscribe to GitHub issue events so every new issue is triaged by an agent and the result is delivered to a Telegram chat automatically. ## 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 for GitHub events?▼

Run `hermes webhook subscribe` with a name, an `--events` filter like "issues", and a `--prompt` template using placeholders such as {issue.title}. The command returns a webhook URL and HMAC secret to paste into your GitHub repository's webhook settings.

How do I trigger an agent from a Stripe payment webhook?▼

Subscribe with `--events "payment_intent.succeeded,payment_intent.payment_failed"` and a prompt referencing fields like {data.object.amount}. Configure the Stripe webhook endpoint to POST to the returned URL with the provided secret.

Can I send webhook notifications without running an LLM agent?▼

Yes, add `--deliver-only` to the subscribe command. The rendered prompt template is dispatched directly to the target adapter such as Telegram or Discord, returning 200 on success and 502 on delivery failure.

Why is my webhook subscription not receiving events?▼

Check that the gateway is running, `curl http://localhost:8644/health` returns ok, and the service's secret matches the one from `hermes webhook list`. Also verify the `--events` filter matches what the service sends and that the URL is reachable through any firewall or NAT.

How are webhook subscriptions secured?▼

Each subscription gets an auto-generated HMAC-SHA256 secret, or you can supply your own with `--secret`. The webhook adapter validates the signature on every incoming POST, and static routes from config.yaml cannot be overwritten by dynamic subscriptions.