Agent Webhook Handler with Claude Code: Result JSON Schema

A production playbook for agent webhook handler in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: Backend teams wiring agent runs into products

The problem

Backend teams wiring agent runs into products need agent webhook handler to run repeatedly against run states, webhook payloads, retries, and signatures. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Define the outer result contract once, let the agent webhook handler skill own body.data, and reject terminal output that does not match the expected schema.

Tradeoffs and failure modes

Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For agent webhook handler, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Result shape

{
  "schema_version": "argo.result.v1",
  "summary": "agent webhook handler completed",
  "body": { "type": "agent_webhook_handler", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo