Skip to main content
Somebody fed the whole tray into the scanner. What lands in your inbox is one PDF holding three supplier invoices, a shipping label and, for reasons nobody will explain, a boarding pass. A Split node cuts that file into pieces by kind, and each kind goes to the Extract node that suits it.
One file, five pages
Five documents
Invoice98%
Shipping label
Boarding pass
NodesCredits85 per pageYou get

The workflow

Each Split rule is one kind of document and one outgoing branch. The invoice rule also carries a partition_key: the field that tells one invoice from the next inside the same rule, so three invoices in a row become three documents rather than one three-page one.

Run it and read the result

Upload the file once. Split decides which pages belong to which rule, so you send nothing per document.

Response

splits says which pages became which document. extractions then carries one entry per document, each tagged with the split_name and the partition it came from, so you never have to work out which invoice a value belongs to.

When it goes wrong

Everything lands in “Other”. Split always emits an Other group for pages that match no rule, and it is empty on a clean run. A full one means your rule descriptions read like labels rather than descriptions. Write what is printed on the page: “a tracking number, a sender and a recipient address, a weight” beats “shipping stuff”. Three invoices come back as one document. That is the rule without a partition_key. The key names the field that changes between documents of the same kind, usually the identifier printed on each one, and it is what turns one three-page invoice group into three invoices. A sparse document extracts with low confidence. The boarding pass in this run returned its flight number at 80% and its seat at 78%, against 97-99% for the invoices. A card with six words on it gives the model little to cite. Treat a low confidence as “have someone look”, not as a failure: see verification and review. The pages are in the wrong order in the source file. Split works by page, so a document interleaved with another cannot be recovered. Fix the scan, or split the file before you upload it. The workflow is rejected when you save it. Once a workflow has a Split node, every Extract needs a branch, and each branch must be a rule id (INVOICE), not the rule’s display name (Invoice).

Next steps

Split

Every rule option, and Split after a Classify node

Sort invoices from receipts

One document per file, routed by kind