Use “Open a document request” in Recued. Open one document request against a Reception drop link and write its checklist.
Open a document request
Use “Open a document request” in Recued. Open one document request against a Reception drop link and write its checklist.
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 “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 “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.
Opening a request
- In Settings → Reception, create a drop link for this client. Recipes cannot mint one —
reception.endpoint.createis an rpc, not a kernel op — so this is a manual step, and the endpoint's config is immutable once created.
- Bind it to the client's contact if you have one. The substrate attaches every uploaded file to the contact you bind at creation, never to whatever address the visitor types. - Turn ON create a data.file entity — without it no file record is created and nothing can be matched.
- Copy the endpoint id and run this recipe with it, the client's name and your record of their email, and the checklist.
- Documents required is one label per line — "2024 tax return", "Photo ID", "Proof of address". These are the labels the matcher classifies uploads against, so write them the way a filename would read.
- Send the client the drop link. They upload with no account, no login, and nothing installed.
⚠ Re-running is safe and is how you edit a list. Adding a line and re-running creates just that line. Removing a line from the config does NOT delete the row — deleting a checklist line is a destructive op and stays a deliberate act.
⚠ The email you enter is the one that gets chased. It is deliberately not read from the upload page: a visitor-typed address is unverified, and mailing it on a schedule would make the pack a relay for whatever a stranger typed.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (32 steps)
endpoint_ref
trim
Trim whitespace from setting endpoint id
client_name
trim
Trim whitespace from setting client name
email_trimmed
trim
Trim whitespace from setting client email
client_email
lowercase
Convert email trimmed to lowercase
email_has_at
compare
Check if client email contains @
matter
trim
Trim whitespace from setting matter
note
trim
Trim whitespace from setting note
labels_split
split
Split setting document labels into parts
label_rows
map
Extract from each item
label_rows_clean
filter
Filter by condition
label_count
count
Count items in label rows clean
has_labels
compare
Check if label count is greater than 0
inputs_valid
all
Check if all conditions are true
inputs_guard
guard
Stop if inputs valid equals
opened_at
date_add
Add 0 seconds to
due_at
date_add
Add setting due days days to
existing_request
?
existing_rows
default
Apply default
existing_count
count
Count items in existing rows
request_exists
compare
Check if existing count is greater than 0
request_create
?
skip: step.request_exists equal true
request_id
coalesce
Use the first available value from: request create record id, existing rows 0 id
request_recorded
compare
Check if request id has data
request_guard
guard
Stop if request recorded equals
request_ref
template
Generate text from a template
existing_docs
?
existing_doc_rows
default
Apply default
existing_labels
pluck
Extract label from each item
new_label_rows
filter
Filter by condition
doc_create
?
added_count
count
Count items in new label rows
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
note
setting
=
matter
setting
=
due days
setting
=
14
client name
setting
=
[object Object]
endpoint id
setting
=
[object Object]
client email
setting
=
document labels
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.