Module triggers 

ORCH-16 (observed tier): the inbound-trigger noun — an HTTP route or hook mapping that opens a turn when something outside the harness fires.

• Hermes — dynamic webhook subscriptions in HERMES_HOME/webhook_subscriptions.json (a flat map route → {description, events, prompt, skills, deliver, deliver_extra{chat_id}, created_at, secret}, written by hermes webhook subscribe) plus static routes under platforms.webhook.extra.routes in config.yaml; each serves POST /webhooks/<route> (gateway/platforms/webhook.py).
• OpenClaw (pinned 2026.7.1-2) — the hooks block in openclaw.json: enabled, path, token, and hooks.mappings[] (id, match{path,source, event}, action wake|agent, agentId, sessionKey, wakeMode, deliver, channel, to, model); when enabled the gateway also serves the built-in POST <path>/wake and POST <path>/agent endpoints (docs/automation/cron-jobs.md#webhooks at the pin). NOTE: openclaw hooks at the pin manages INTERNAL lifecycle hook packs, not these.
• Claude Code — channels are declared over the MCP protocol at connect time, not in a file; refused rather than guessed (as ORCH-14).

Read-only, and no secret is ever read for anything but presence: the per-route HMAC secret (Hermes) and the hook token (OpenClaw) are never emitted.

Structs

TriggerDeliver

Where the reply is delivered.

TriggerRow

One inbound trigger.

TriggerTarget

Where the fired turn goes.

Enums

TriggerError

Why a listing was refused.

TriggerKind

What kind of trigger a row is.

Constants

TRIGGERS_SCHEMA

Wire schema of harness.v1.triggers.list.

TRIGGER_HARNESSES

Harnesses with an inbound-trigger concept supercode can read.

Functions

list_triggers

List inbound triggers, optionally for one harness.