mission-data-webhooks

Points to the user-facing documentation and reference example for Overlord's mission-data webhooks feature. Invoke when building, debugging, or explaining a webhook consumer, when asked how to receive mission events (delivery, status change, blocked) outside this repository, or when touching webhook_subscriptions/outbox_messages/webhook-dispatcher code.

Jump to install

Repository: cooperativ-labs/Overlord
Last source activity: July 14, 2026 at 15:43
Detected SKILL.md language: English
Stars: 4
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/cooperativ-labs/Overlord --skill mission-data-webhooks

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Mission Data Webhooks

Overlord can push signed HTTP deliveries to an external endpoint on mission events, so independent software (a feed-post generator, a memory ingester, a production-test trigger, anything else) can react without living inside this repository or its runtime.

Building or debugging a webhook consumer (signature verification, payload envelope, retry/ idempotency semantics, thin-vs-full payload mode, the REST pull path for anything a thin payload omits).

Answering a user's question about how to receive mission events outside Overlord.

Explaining or modifying webhook management (Settings → Webhooks, /api/webhooks*).

A complete, runnable reference consumer lives at examples/webhook-consumers/feed-post-generator/ — it rebuilds the upstream Overlord generate-feed-post pipeline as ordinary external software driven by this webhook, and is the pattern to point users at when they ask "how do I build a consumer."

If you are implementing inside this repository

The feature's own architecture doc is planning/feature-plans/mission-data-webhooks-api.md. Key source files, in the order an event flows through them:

packages/core/service/webhook-events.ts — enqueueWebhookEvent() (the shared-single-writer enqueue helper, called from both the protocol service core and the REST data layer) and buildWebhookEnvelope() (thin/full envelope hydration).

backend/webhook-dispatcher.ts — the in-process, RealtimeHub-style polling worker that claims outbox_messages rows and delivers HMAC-signed HTTP POSTs with retry/backoff.

backend/webhook-security.ts — SSRF guard, OVERLORD_WEBHOOK_INTERNAL_HOSTS internal-host detection, and Stripe-style signature generation.

backend/webhooks.ts + the /api/webhooks* routes in backend/index.ts — subscription management (list/create/update/delete/rotate-secret/test/deliveries/redeliver).

webapp/web/components/settings/WebhooksPage.tsx — the management UI.

Adding a new webhook event type or touching the tables (webhook_subscriptions, webhook_delivery_attempts, outbox_messages) is a cross-module change — read CONTRACT.md and the database schema contract's "Webhook event catalog" section first, per the component-contract skill.