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
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 “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 “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
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. The reconciliation id is keyed on the request and the exact outstanding set, so re-running with nothing changed will not double-send; but once a document arrives 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.
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]
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.