CRM Enrichment with Codex: API Runtime Pattern
A production playbook for CRM enrichment in cross-industry operations using Codex: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Revenue systems teams
The problem
Revenue systems teams need CRM enrichment to run repeatedly against account records, call notes, research docs, and enrichment 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
Package the CRM enrichment instructions as a skill, send account records, call notes, research docs, and enrichment rules 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 CRM enrichment, 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=crm-enrichment
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo