webhook-subscriptions

Create webhook subscriptions that trigger ZedClaw runs from external POST requests.

4|Updated May 18, 2026
One-click install
npx skills add https://github.com/ZardLi1115/zedclaw --skill webhook-subscriptions-zardli1115
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhook-subscriptions
Source: https://github.com/ZardLi1115/zedclaw/tree/main/skills/devops/webhook-subscriptions
Command: npx skills add https://github.com/ZardLi1115/zedclaw --skill webhook-subscriptions-zardli1115

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill solves the problem of manually starting agent workflows by enabling external systems to trigger ZedClaw automatically whenever important events occur.

Core Features & Use Cases

  • Create event-driven subscriptions: Define which incoming events should trigger an agent run, using prompt templates with payload dot-notation for nested fields.
  • Route events to the right agents and notifications: Forward agent results to configured delivery targets (e.g., Telegram, Discord, GitHub comments) or deliver verbatim messages without LLM cost.
  • Secure and reliable triggering: Use HMAC-SHA256 signing with per-subscription secrets, persist subscriptions locally, and allow retry-friendly test and health verification.
  • Use case: Automatically triage new GitHub issues by sending a formatted prompt (including issue title/body/author) to ZedClaw and notifying your team in chat.

Quick Start

Set up the webhook gateway and create a subscription by running zedclaw webhook subscribe github-issues --events "issues" --prompt "New GitHub issue #{issue.number}: {issue.title}" --skills "github-code-review" --deliver telegram --deliver-chat-id "123456789" .

Frequently Asked Questions about webhook-subscriptions

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

FAQPage Schema
How do I trigger agent runs automatically from GitHub webhooks?

You can trigger agent runs from GitHub webhooks by creating event-driven subscriptions that send POST requests to a configured gateway. The system uses prompt templating with payload dot-notation to format issue or PR data into dynamic prompts for the agent.

Can I use HMAC signature validation to secure incoming webhook notifications?

Yes, HMAC-SHA256 signature validation secures incoming webhook notifications. Each subscription uses per-subscription signing secrets to verify payload authenticity, ensuring only trusted external service events trigger agent workflows.

How do I route Stripe payment lifecycle notifications to chat platforms?

Stripe payment lifecycle notifications can be routed to chat platforms by configuring delivery targets like Telegram or Discord within a webhook subscription. You can forward agent results or deliver verbatim messages directly to a specified chat ID without LLM cost.

What's the best way to format webhook payloads into dynamic prompt templates?

The best way to format webhook payloads into dynamic prompt templates is using payload dot-notation rendering. This allows you to extract nested fields like issue title, body, or author from incoming POST requests and inject them directly into the agent prompt.

Do I need a configured webhook platform to automate CI/CD pipeline alerts?

Yes, you need a configured webhook platform with persistent subscription storage to automate CI/CD pipeline alerts. The platform receives external POST requests, validates HMAC signatures, and routes the extracted event data to trigger the appropriate agent run.

Why deliver webhook event messages verbatim instead of through an LLM agent?

Delivering webhook event messages verbatim avoids LLM processing costs when raw notification forwarding is sufficient. This direct delivery mode routes incoming alerts straight to configured targets like Telegram or Discord without triggering an agent run.