The Dangerous Part Is Not Extraction. It Is Trusting Everything. Most n8n document workflows start with a clean demo: a PDF arrives, a document node extracts fields, and a spreadsheet or database node writes the result. That is fine until the workflow starts handling real documents. A supplier invoice has a smudged total. A receipt uses a currency symbol the parser is not fully sure about. A contract date appears twice, once in the header and once in a clause. The workflow still writes a row because every extracted value was treated as equally trustworthy. The fix is not to send every document to a human. That kills the value of automation. The better pattern is to let high-confidence fields continue automatically and route only uncertain fields to a review branch. n8n is a good fit for this because the canvas can make the decision path explicit: extract, inspect confidence, branch, review, resume. Model Review as a Branch, Not a Failure Low confidence is not the same as an error.…