Recued
Menu
← Back to recipes

Chase the missing documents

by recued-core v2 7 views

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

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 “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
View pack details, dependencies, and permissions →

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 25 steps

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

Process (25 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 ?
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 ?
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
reconciliation template
Generate text from a template
chase_send ?
chase_reconcile ?
card to_summary
Format results as a summary card
Settings 3 configurable

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.

Data it touches

Warehousedata.mail

About

Tags

pack:client-document-intakedocumentschecklistmailrecordsv2

Details

25 steps 3 configurable settings recipe_id: chase-missing-documents