webhook-subscriptions

Manage webhook subscriptions that trigger agent runs from HTTP POST events.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/thisismynewfmail-ui/Monika-agent --skill webhook-subscriptions-thisismynewfmail-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhook-subscriptions
Source: https://github.com/thisismynewfmail-ui/Monika-agent/tree/main/skills/devops/webhook-subscriptions
Command: npx skills add https://github.com/thisismynewfmail-ui/Monika-agent --skill webhook-subscriptions-thisismynewfmail-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable external services to automatically activate Monika agent workflows by turning incoming HTTP POST events into contextual agent runs, removing manual polling and bridging third-party event sources into automated responses.

Core Features & Use Cases

  • Create and manage subscriptions: Easy CLI-based creation, listing, testing, and removal of named webhook subscriptions.
  • Secure delivery: Per-subscription HMAC-SHA256 secrets with signature validation and optional custom secrets.
  • Flexible routing and templating: Event filtering, prompt templates using dot.notation for nested JSON, and configurable delivery targets (Telegram, Discord, GitHub comments, origin, etc.).
  • Hot-reload and persistence: Subscriptions persist to ~/.monika/webhook_subscriptions.json and the adapter hot-reloads changes with minimal overhead.
  • Real-world examples: GitHub issue triage, PR review notifications, Stripe payment alerts, CI/CD build notifications, and generic monitoring/IoT alerts.

Quick Start

Create a new webhook subscription that triggers a Telegram notification for GitHub issue events by running the monika webhook subscribe command with an appropriate events filter and prompt template.

Frequently Asked Questions about webhook-subscriptions

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

FAQPage Schema
How do I trigger automated agent workflows from external webhook events?

Webhook subscriptions allow external HTTP POST events to trigger agent runs by turning incoming payloads into contextual automated responses. This removes manual polling and bridges third-party event sources like GitHub, Stripe, or IoT sensors into automated triage and notifications.

Can I validate webhook signatures with HMAC-SHA256 for secure delivery?

Yes, secure delivery is supported through per-subscription HMAC-SHA256 secrets with signature validation. You can use optional custom secrets to verify that incoming HTTP POST events from external services are authentic before triggering agent workflows.

How do I filter incoming events and format payloads using prompt templating?

Event filtering and prompt templates using dot.notation for nested JSON allow flexible routing of webhook events. This lets you extract specific payload fields and format contextual prompts so the agent runs only process relevant triggered data.

Does webhook automation work with GitHub, Stripe, and CI/CD systems?

Webhook subscriptions apply to CI/CD systems, code hosting platforms like GitHub and GitLab, payment gateways such as Stripe, monitoring tools, and IoT sensors. They automate triage, notifications, reviews, and incident response directly from these external HTTP POST events.

What's the best way to send webhook alerts to Telegram and Discord?

Configurable delivery adapters route webhook events to Telegram, Discord, and GitHub comments. By setting up named subscriptions with appropriate event filters and prompt templates, automated notifications are delivered directly to your chosen platforms when triggered.

How are webhook subscriptions stored and updated without restarting?

Subscriptions persist to a JSON file and the adapter hot-reloads changes with minimal overhead. This means you can create, list, test, and remove webhook subscriptions dynamically without interrupting active event listeners.