hooks-automation

Name: hooks-automation
Availability: InStock
Author: Acosmi

Trigger agent runs from external HTTP webhook events.

6|Updated Feb 26, 2026

Search Tags:#automation #webhook #ci integration #external event #event routing #github webhook #http callback

Ready to run

npx skills add https://github.com/Acosmi/CrabClaw --skill hooks-automation-acosmi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hooks-automation
Source: https://github.com/Acosmi/CrabClaw/tree/main/docs/skills/operations/hooks-automation
Command: npx skills add https://github.com/Acosmi/CrabClaw --skill hooks-automation-acosmi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables reliable webhook-driven automation to trigger agent runs in response to external HTTP events, enabling seamless integration with external systems.

Core Features & Use Cases

Webhook endpoints: Expose /hooks/agent and related endpoints to receive HTTP events and start agent workflows.
hooks.mappings: Use mappings to route incoming payloads to sessions and control delivery of results.
Use Case: Connect GitHub, GitLab, Gmail, CI systems, or other webhook sources to automatically trigger automated agent tasks and deliver outcomes to a channel or API.

Quick Start

Send a webhook POST to /hooks/agent to trigger an immediate agent run.

Frequently Asked Questions about hooks-automation

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

FAQPage Schema

How do I trigger an automated agent run from a GitHub webhook?▼

You can trigger an automated agent run from a GitHub webhook by sending an HTTP POST request to the /hooks/agent endpoint. This enables reliable webhook-driven automation for external systems like GitHub.

What is webhook-driven automation for external event routing?▼

Webhook-driven automation for external event routing exposes endpoints to receive HTTP callbacks and start agent workflows. It applies configurable mappings to route incoming payloads from external systems to specific sessions.

How do I configure mappings to route incoming webhook payloads?▼

You configure hooks.mappings to route incoming webhook payloads to sessions and control the delivery of results. This allows you to direct HTTP-triggered events from services like GitLab or Gmail to the correct automated workflow.

Can I use HTTP callbacks from Gmail or CI pipelines to trigger agent tasks?▼

Yes, you can use HTTP callbacks from Gmail, CI pipelines, GitLab, and other webhook sources to trigger agent tasks. The solution supports HTTP-triggered events with configurable mappings and delivery.

Does this webhook automation solution support authentication headers?▼

Yes, this webhook automation solution supports authentication headers for integrated gateway-based setups. It satisfies the requirements for an integrated gateway-based webhook solution with endpoint definitions and authentication.

What is the best way to integrate external CI systems with an agent gateway?▼

The best way to integrate external CI systems with an agent gateway is to expose /hooks/agent endpoints to receive HTTP events. This allows external systems to automatically trigger automated agent tasks and deliver outcomes to a channel or API.