Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Records runtime compatibility canary
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
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 “Chase the missing documents” in Recued. Email one client the list of documents still outstanding, with their drop link.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.