Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Update Name and Description
What This Skill Does
Hookaido is a webhook gateway that accepts inbound HTTP requests, queues them, and delivers them to consumers via pull or push. It supports sqlite, memory, and postgres queue backends and exposes HTTP and gRPC pull APIs. Config is declarative via Hookaidofile with built-in auth, retry, and dead-letter queue handling.
Unlike generic message brokers, Hookaido covers the full webhook lifecycle, ingress auth, queuing, pull or push delivery, and DLQ management, without requiring a separate broker deployment for common webhook scenarios.
When to use it
- Ingesting GitHub push events and letting workers dequeue at their own pace
- Retrying failed Stripe webhook deliveries with exponential backoff
- Draining a dead-letter queue after a downstream service outage
- Running MCP mode to let an AI agent inspect queue health and backlog
- Switching from in-memory queuing to Postgres for a shared multi-worker setup
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Set up GitHub webhook ingestion with HTTP pull consumption using a SQLite queue
- 1Write a Hookaidofile with an ingress listener, pull_api block, and a /webhooks/github route with HMAC auth pointing to a pull path
- 2Run `hookaido config fmt --config ./Hookaidofile` then `hookaido config validate --config ./Hookaidofile`
- 3Start the runtime with `hookaido run --config ./Hookaidofile --db ./.data/hookaido.db`
- 4Verify health via `curl http://127.0.0.1:2019/healthz?details=1`
- 5Send a test webhook payload and exercise the dequeue/ack cycle against the pull API
GitHub webhook events are accepted, queued in SQLite, and available for workers to dequeue and acknowledge over HTTP
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.