Administrative Inbox Routing with Claude Code: API Runtime Pattern
A production playbook for administrative inbox routing in administrative operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Back-office administrative teams
The problem
Back-office administrative teams need administrative inbox routing to run repeatedly against emails, attachments, sender metadata, policy rules, and routing labels. In administrative operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the administrative inbox routing instructions as a skill, send emails, attachments, sender metadata, policy rules, and routing labels as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For administrative inbox routing, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=admin-inbox-routing
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo