Skip to content

gitflarePublicPartly agent-ready50

cf-workflows-pipeline

Durable content pipeline on Cloudflare Workflows: ingest, extract, summarise with Workers AI via AI Gateway, human approval, publish.

Fix pipeline runs failing at ingest (steps.attempt NOT NULL)629b2fa
Markdown13 lines964 B

API

Errors: { "error": { "code": "bad_request|not_found|method_not_allowed|conflict|internal_error", "message": "..." } }.

  • POST /api/runs body { url? | text?, length?: short|medium|long, failures?: { extract?, summarise?, publish? } } → 201 { id }. URLs must be http/https, not localhost or a private IP literal.
  • GET /api/runs → { runs: [{ id, status, source, length, created_at, updated_at }] } (latest 50).
  • GET /api/runs/:id → { run, steps: [{ name, state, label, attempt, durationMs, output, error }], instance }.
  • POST /api/runs/:id/approve and /reject body { note? } → { ok: true }; 409 unless status is awaiting_approval.
  • GET /p/:id → public HTML page for a published run, 404 otherwise.
  • GET /health.

Run status: queued, running, awaiting_approval, published, rejected, failed. If Workers AI fails, summarise falls back to an extractive summary and its output is prefixed [fallback: extractive].