Recued
Menu
← Back to recipes

Document requests board

by recued-core v2 6 views

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.

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 “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.

pack:client-document-intakedocumentschecklistboard
by recued-core pinned v2

Use “Open a document request” in Recued. Open one document request against a Reception drop link and write its checklist.

pack:client-document-intakedrop-linkreceptiondocuments
by recued-core pinned v2

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.

pack:client-document-intakedrop-linkreceptiondocuments
by recued-core pinned v2

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.

pack:client-document-intakedocumentschecklistrecords
by recued-core pinned v2

Use “Chase the missing documents” in Recued. Email one client the list of documents still outstanding, with their drop link.

pack:client-document-intakedocumentschecklistmail
by recued-core pinned v2
View pack details, dependencies, and permissions →

Working the board

Stage picks what you are looking at:

  • proposed — lines the matcher believes are satisfied, waiting on you. This is the queue that needs a human.
  • missing — still outstanding, nothing proposed.
  • received — you accepted them.
  • all — everything, newest first.

The Confirm row action opens Confirm a document with the line already filled in, so a line id never gets retyped.

proposed is not received. A proposal is the matcher's guess from a filename — see Match a dropped document for why it can never be more than that.

⚠ A page is at most 100 lines. Narrow with Stage rather than raising the limit.

How it works 19 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (19 steps)
row_limit clamp
Clamp setting limit between 1 and 100
show_all compare
Check if setting stage equals all
docs_filtered ?
skip: step.show_all equal true
docs_all ?
skip: step.show_all equal false
doc_rows coalesce
Use the first available value from: docs filtered records, docs all records
rows default
Apply default
request_refs pluck
Extract request_ref from each item
requests ?
request_rows default
Apply default
request_index map
Extract from each item
rows_with_client enrich_by
Apply enrich_by
board_rows map
Extract from each item
missing_count ?
proposed_count ?
received_count ?
open_requests ?
shown_count count
Count items in rows
board_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 2 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

limit setting = 50
stage setting = proposed

About

Tags

pack:client-document-intakedocumentschecklistboardread-onlyrecordsv2

Details

19 steps 2 configurable settings recipe_id: list-document-requests