webhook-subscriptions

Create and manage webhook subscriptions triggering Xerxes runs from external events.

27|2|Updated Jan 15, 2024
One-click install
npx skills add https://github.com/erfanzar/Xerxes-Agents --skill webhook-subscriptions-erfanzar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhook-subscriptions
Source: https://github.com/erfanzar/Xerxes-Agents/tree/main/src/python/xerxes/skills/webhook-subscriptions
Command: npx skills add https://github.com/erfanzar/Xerxes-Agents --skill webhook-subscriptions-erfanzar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and manage webhook subscriptions so external services can trigger Xerxes agent runs by POSTing events to a URL, enabling event-driven automation and reducing manual intervention.

Core Features & Use Cases

  • Webhook subscriptions: create, configure, and manage endpoints that route events to Xerxes.
  • Flexible delivery: support multiple delivery targets per subscription (Telegram, Discord, GitHub comments, or custom integrations) and per-subscription prompts.
  • Security-first by design: each subscription has an auto-generated HMAC secret to validate incoming payloads and prevent tampering.

Quick Start

Enable the webhook platform and create a subscription that triggers an Xerxes run when an external event is posted to the webhook URL.

Frequently Asked Questions about webhook-subscriptions

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

FAQPage Schema
How do I create webhook subscriptions to trigger agent runs from external events?

Create webhook subscriptions by enabling the webhook platform and configuring a URL endpoint that routes incoming POST events to trigger Xerxes agent runs. You can set this up through the configuration workflow or environment variables.

Can I configure webhook subscriptions to deliver events to Telegram or Discord?

Yes, webhook subscriptions support multiple delivery targets per endpoint, including Telegram, Discord, GitHub comments, and custom integrations. You can configure these delivery destinations alongside per-subscription prompts.

How does HMAC validation work for securing incoming webhook payloads?

HMAC validation uses an auto-generated secret per subscription to verify incoming payloads and prevent tampering. Each webhook subscription automatically receives this secret to authenticate external event requests.

What's the best way to set up event-driven automation with GitHub or Stripe webhooks?

The best way is creating a webhook subscription that receives GitHub or Stripe event POSTs and triggers Xerxes agent runs automatically. This enables event-driven automation across services that emit events, reducing manual intervention.

Do I need a config.yaml file to manage webhook subscriptions?

No, configuration is flexible and supports both config.yaml and environment variables for managing webhook subscriptions. You can use either method to define endpoints, prompts, and delivery targets for your automation workflows.