Use “Chase the missing documents” in Recued. Email one client the list of documents still outstanding, with their drop link.
Chase the missing documents
Use “Chase the missing documents” in Recued. Email one client the list of documents still outstanding, with their drop link.
Complete workflow
Client Document Intake
9 pinned recipes
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 “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 “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.
Chasing a client
Run it with the request id (the board and the opener both print it) and the public URL of their drop link.
It reads the request, collects every line still missing, and sends one email listing them with the link. A line sitting at proposed is NOT chased — something arrived for it and it is waiting on you, not on the client.
⚠ It refuses when nothing is outstanding. That is the point: the whole failure mode of a chase automation is mailing someone for a document they already sent.
⚠ The drop link URL is passed in, not derived. No recipe can read or mint a Reception endpoint's public URL — copy it from Settings → Reception. Pinning it here also means you can send a chase for a link you have since rotated without the pack silently mailing a dead URL it cached.
⚠ Re-running sends again only when the list changed. The reconciliation id is keyed on the request and the exact outstanding set, so re-running with nothing changed does not double-send, and the card says it was already sent; once a document arrives, or you ask for another, the set changes and a fresh chase becomes sendable. Chasing on a schedule is a dish, not a flag on this recipe.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (31 steps)
request_id
trim
Trim whitespace from setting request id
drop_url
trim
Trim whitespace from setting drop link url
drop_url_https
starts_with
Check if drop url starts with https://
sender_mail
trim
Trim whitespace from setting sender mail instance
inputs_valid
all
Check if all conditions are true
inputs_guard
guard
Stop if inputs valid equals
request
recued-core.client-document-intake.request.get
Get request on client document intake
found
compare
Check if request record exists
found_guard
guard
Stop if found equals
client_email
default
Apply default
email_present
compare
Check if client email has data
email_guard
guard
Stop if email present equals
request_ref
template
Generate text from a template
outstanding
recued-core.client-document-intake.required_doc.search
Search required doc on client document intake
outstanding_rows
default
Apply default
outstanding_count
count
Count items in outstanding rows
has_outstanding
compare
Check if outstanding count is greater than 0
nothing_outstanding_guard
guard
Stop if has outstanding equals
outstanding_labels
pluck
Extract label from each item
outstanding_list
join
Join items with "
- "
defaults
defaults
Apply defaults
outstanding_sorted
sort
Sort by id
outstanding_ids
pluck
Extract id from each item
outstanding_ids_text
join
Join items with ","
outstanding_key
sha256
Apply sha256
reconciliation
template
Generate text from a template
chase_send
core.mail.send
Send mail
chase_reconcile
core.mail.sent.reconcile
Reconcile mail sent
already_sent
default
Apply default
delivery_note
ternary
Apply ternary
card
to_summary
Format results as a summary card
▼
Output
summary
card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
request id
setting
=
[object Object]
drop link url
setting
=
sender mail instance
setting
=
[object Object]
Uses (4 operations)
Pack operation
Get request on client document intake
recued-core.client-document-intake.request.get
Pack operation
Search required doc on client document intake
recued-core.client-document-intake.required_doc.search
Mail
Send mail
core.mail.send
Mail
Reconcile mail sent
core.mail.sent.reconcile
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
Read
Pack
Client Document Intake
read-only
Read: request.get · No approvalRead: required_doc.search · No approval
Write
Mail
core.mail.send
external change
Write
Mail
core.mail.sent.reconcile
external change