Email Intake Routing with Claude Code: Artifact Delivery
A production playbook for email intake routing in cross-industry operations using Claude Code: artifact delivery, run-scoped inputs, logs, typed results, and artifacts.
Audience: Shared inbox and intake teams
The problem
Shared inbox and intake teams need email intake routing to run repeatedly against email bodies, attachments, sender metadata, and routing rules. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Require Claude Code to write customer-visible files under /skill/output/artifacts, validate filenames and sizes, then return signed artifact metadata in argo.result.v1.
Tradeoffs and failure modes
Artifact policy constrains file output, but customers receive files that are durable, typed, and safe to download. For email intake routing, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Artifact manifest
artifacts:
- email-intake-routing-summary.md
- email-intake-routing-evidence.csv
- email-intake-routing-review.json
signed_urls: true
retention: org_policy
Run this on Argo