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.
Confirm a document
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.
Complete workflow
Client Document Intake
6 pinned recipes
Use Client Document Intake in Recued for drop link, reception, documents, and checklist. It includes 14 built-in actions and 5 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 “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.
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.
Accepting or clearing a proposal
Run it from the board's row action, or by hand with the checklist line's id.
- accept — the proposed file becomes the line's
file_ref, status goes toreceived, andreceived_atis stamped with the time YOU accepted (not when the file landed; those differ, sometimes by days). - clear — the proposal is dropped and the line goes back to
missing. Use it when the matcher credited the wrong line; the next upload can then be matched against it.
⚠ It refuses a line with no proposal on it. There is nothing to accept, and writing received against no file would leave a checklist claiming a document you do not have.
⚠ Open the file before you accept it. A drop is unscanned unless you run a scanner pack, and this recipe reads nothing but the record id — it makes no claim about what the file contains.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (14 steps)
doc_id
trim
Trim whitespace from setting required doc id
id_guard
guard
Stop if doc id is empty
doc
?
found
compare
Check if doc record exists
found_guard
guard
Stop if found equals
proposed_file
default
Apply default
has_proposal
compare
Check if proposed file has data
proposal_guard
guard
Stop if has proposal equals
accepting
compare
Check if setting decision equals accept
received_at
date_add
Add 0 seconds to
accept_doc
?
skip: step.accepting equal false
clear_doc
?
skip: step.accepting equal true
final_status
coalesce
Use the first available value from: accept doc record status, clear doc record status
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
decision
setting
=
accept
required doc id
setting
=