webhook-subscriptions

Create and manage webhook subscriptions that trigger agent runs via HTTP POST events.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Webhook subscriptions remove the need for manual polling and ad-hoc event handling by letting external services automatically trigger agent runs when relevant events occur. This enables faster, consistent, and automated responses to events such as new issues, payment notifications, CI builds, or monitoring alerts.

Core Features & Use Cases

  • Create and manage subscriptions: register named routes that map incoming POST events to prompt templates and skill handlers.
  • Secure delivery: per-subscription HMAC-SHA256 secrets and signature validation to ensure authentic requests.
  • Flexible routing and delivery: filter by event types, format payloads into prompts, and deliver responses to targets like Telegram, Discord, or GitHub comments.
  • Persistence and hot-reload: subscriptions persist to disk and are hot-reloaded by the adapter so changes take effect immediately.
  • Use Case: triage new GitHub issues into a Telegram channel, post CI build summaries to Discord, or run payment-event workflows for Stripe notifications.

Quick Start

Use the webhook-subscriptions skill to create a subscription that listens for GitHub issues and delivers triage results to your Telegram channel.

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 runs from external webhook events?

You can trigger automated agent runs by creating webhook subscriptions that map incoming HTTP POST events to specific prompt templates and skill handlers, eliminating the need for manual polling.

How do I verify external webhook payloads for GitHub or Stripe integrations?

Webhook payload verification is handled using per-subscription HMAC-SHA256 secrets and signature validation, ensuring that incoming requests from services like GitHub or Stripe are authentic.

Can I route incoming webhook events to Telegram or Discord notifications?

Yes, you can route incoming JSON payloads to configurable delivery targets including Telegram, Discord, and GitHub comments by formatting the payloads into prompts for delivery.

How do I filter webhook subscriptions by event types like CI builds or payment notifications?

Event filtering allows you to specify criteria for incoming webhook payloads, ensuring that only relevant events such as CI build summaries or Stripe payment notifications trigger the mapped agent runs.

Do I need to restart my services when hot-reloading webhook routes?

No, route hot-reloading applies subscription changes immediately without requiring a restart, and persistent subscription storage ensures your configurations are saved to disk.

What is the best way to manage automated event handling for IoT or monitoring alerts?

Managing automated event handling is best achieved by registering named webhook routes that automatically process incoming JSON payloads from IoT devices or monitoring alerts into formatted prompts.