Customer Health Review with Codex: API Runtime Pattern
A production playbook for customer health review in cross-industry operations using Codex: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Customer success leaders
The problem
Customer success leaders need customer health review to run repeatedly against usage exports, support history, renewal notes, and account plans. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the customer health review instructions as a skill, send usage exports, support history, renewal notes, and account plans as run-scoped inputs, execute with Codex, 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 customer health review, 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=codex
workflow=customer-health-review
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo