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.
Document requests board
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.
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 “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.
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.
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.
Working the board
Stage picks what you are looking at:
proposed— lines the matcher believes are satisfied, waiting on you. This is the queue that needs a human.missing— still outstanding, nothing proposed.received— you accepted them.all— everything, newest first.
The Confirm row action opens Confirm a document with the line already filled in, so a line id never gets retyped.
⚠ proposed is not received. A proposal is the matcher's guess from a filename — see Match a dropped document for why it can never be more than that.
⚠ A page is at most 100 lines. Narrow with Stage rather than raising the limit.
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
stage
setting
=
proposed
Uses (4 operations)
recued-core.client-document-intake.required_doc.search
recued-core.client-document-intake.request.search
recued-core.client-document-intake.required_doc.count
recued-core.client-document-intake.request.count
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.