Human Approval for AI Content Pipelines

Description and use

Adding an approval gate before publishing in an AI content pipeline prevents accidental releases and allows human edits before final publish.

Problem

AI content pipelines can publish drafts without human oversight, risking public mistakes at the publish step.

Outcome

Adding a gate at the publish step prevents accidental public releases, allows human edits before final publish, and supports multi‑channel approvals with minimal round‑trips.

Workflow

• 1. Draft content via AI agent. 2. Generate social snippets. 3. Call Impri /v1/actions to request approval, providing title, preview, and target URL. 4. Wait for approval status via polling /v1/actions/{id}. 5. If approved, publish to CMS using the final preview body. 6. Mark action as executed; if rejected or expired, abort publish.

Evidence

What blocks execution is a status field the publish code checks before it runs — which is what Impri's /v1/actions gate gives you.

Source

The wrapper only works as a real gate if cms_publish() is unreachable except through the code path above.

Source