How-To Series · Episode 34 / 59 · Module 5: Everywhere You Are
Hermes · Webhooks
If a tool can POST to a URL, it can trigger Hermes.
After this videoYou can now trigger Hermes from any external system.
The webhook adapter runs an HTTP server on port 8644. Anything POSTs JSON to /webhooks/<route>, Hermes validates the HMAC signature, turns the payload into a prompt, runs the agent, and delivers the answer. Enable it, then define routes in config.yaml with a prompt template using {dot.notation} (e.g. {pull_request.title}). Deliver back as a github_comment or to any connected platform. The money saver: deliver_only: true skips the agent entirely (zero tokens, sub-second) for plain alerts. Create routes on the fly with hermes webhook subscribe. Every route needs an HMAC secret; sandbox the gateway since payloads are attacker-controlled.
About these resources. Every command in this video comes from the Webhooks doc.
Sources · What this video distills
1 docs page · every command below traces to one of themCommands shown · Copy and paste
each shows the source doc it came fromWEBHOOK_ENABLED=true WEBHOOK_PORT=8644 WEBHOOK_SECRET=your-global-secretcurl http://localhost:8644/healthhermes webhook subscribe alerts --deliver telegram --deliver-only --prompt "Alert: {__raw__}"Going deeper · Related Hermes docs
further reading · not sources of facts shown aboveNext in the series · Episodes that build on this
E30
Hermes on SMS
E36
Schedule With Cron
E40
Event Hooks