Flag for review
Module · Stable
Park an extraction on /inbox for a human to confirm or dismiss, instead of writing it (or in addition to a row that already exists).
Persists an extraction as a pending review — the same queue Ingest into Table already writes to when it reports a low-confidence “held” result, now reachable directly from a flow for any reason a document needs a person’s judgement: it might not be an invoice at all, it might be the wrong kind, or the numbers might not add up. The review surfaces on /inbox with Accept (writes the fields into the table via its bound recipe — a human confirming “yes this is right” is one click, no re-upload) and Dismiss (records the decision, writes nothing). Never silently drops a document a flow is unsure about.
When to use
Section titled “When to use”Use when a flow-level check (a classifier saying “not an invoice” or “wrong category”, a business-rule mismatch) means a document should NOT go straight through, but also should not be silently discarded. Branch on the check first, then call this instead of the normal write step. Pair with a notification so the reviewer actually learns something is waiting.
When not to use
Section titled “When not to use”For the low-confidence case Ingest into Table already detects (its needs_review flag), you do not need this AS WELL for the same document unless you are branching on a DIFFERENT check upstream of ingestion — Ingest into Table only auto-holds on confidence, not on a classifier result. If you just want to tell someone something happened (not ask them to confirm/reject it), use Send notification instead — this step is specifically for a document that needs a yes/no human decision.
Inputs
Section titled “Inputs”Configured per use: table, source_doc_id, recipe_key, recipe_version, fields, overall_confidence, reason.
Outputs
Section titled “Outputs”Auto-generated from the skill registry (load_skills()). Do not edit by hand.