Use “Accept documents in bulk” in Recued. Tick the proposals you believe and accept them in one go. Same decision as confirming one line, made once for several — the board stays the board, and this is where a batch is done.
Accept documents in bulk
Use “Accept documents in bulk” in Recued. Tick the proposals you believe and accept them in one go. Same decision as confirming one line, made once for several — the board stays the board, and this is where a batch is done.
Complete workflow
Use Client Document Intake in Recued for drop link, reception, documents, and checklist. It includes 14 built-in actions and 8 ready-to-run workflows. Actions that change data use Recued's approval controls.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Open a document request” in Recued. Open one document request against a Reception drop link and write its checklist.
Use “Match a dropped document” in Recued. Fires when a file lands in the relevant record and proposes which outstanding checklist line it satisfies. It proposes only — the line stays missing until you confirm it.
Use “Confirm a document” in Recued. Accept the proposal on one checklist line, or clear it. This is the step that turns a file arriving into a document received — the two are different facts and the pack keeps them apart.
Use “Repair blank checklist lines” in Recued. Remove the empty checklist lines a defect wrote before 21 September 2026, so a request opened with no documents stops showing a line whose label is a leftover placeholder. It asks before each removal, and it never deletes the request itself.
Use “Document requests board” in Recued. Every open document request with what is still outstanding, and every line waiting on your decision. It reads information without changing data in the connected service.
Show all 9 recipes
Use “Chase the missing documents” in Recued. Email one client the list of documents still outstanding, with their drop link.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Use “One required doc” in Recued. Open one required doc from the list that names it, and read everything recorded about that required doc on one page.
Accepting several proposals at once
The table lists every checklist line currently sitting at proposed — a file arrived and something matched it to a line. Tick the ones you believe, then press Accept selected.
Accepting means the same thing here as it does on one line: the proposed file becomes the line's file_ref, the status moves to received, and received_at is stamped with the time YOU accepted — not when the file landed.
⚠ Open the files before you tick them. A drop is unscanned unless you run a scanner pack, and this recipe reads nothing but record ids. Ticking eight rows makes eight claims about documents you have not looked at.
⚠ Only the ids travel. Everything else — which file is on the proposal, the record's revision — is re-read fresh when you press the button, so a line whose proposal was cleared while you were reading simply drops out of the batch rather than being written against stale state.
⚠ To CLEAR a wrong proposal, use “Confirm a document” on that line. Clearing is a per-line judgement about a specific mismatch, and a bulk clear would make it easy to throw away several matches with one press.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
limit
setting
=
50
cursor
setting
=
accept ids
setting
=
Uses (3 operations)
recued-core.client-document-intake.required_doc.get_many
recued-core.client-document-intake.required_doc.update
recued-core.client-document-intake.required_doc.search
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.