Use “Show what a search found” in Recued. List the documents one search run matched, with the page and the matching line, alongside the documents that could not be opened. Read-only.
Show what a search found
Use “Show what a search found” in Recued. List the documents one search run matched, with the page and the matching line, alongside the documents that could not be opened. Read-only.
Complete workflow
Document Search
6 pinned recipes
Use Document Search in Recued for PDF, retrieval, pdfgrep, and records. It includes 11 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 “Search your documents” in Recued. Search every PDF in a folder for a term and record which documents matched, with the page and the matching line. Each file is first checked as readable, so a document that could not be opened is reported as unreadable rather than counted as a miss.
Use “Show past document searches” in Recued. List search runs with their counts, including how many documents could not be opened. Read-only — it re-reads no file and re-runs no search.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Use “One search” in Recued. Open one search from the list that names it, and read everything recorded about that search on one page.
Use “One hit” in Recued. Open one hit from the list that names it, and read everything recorded about that hit on one page.
Reading the hits
Outcome is matched or unreadable. Documents that were searched and genuinely did not contain the term are not listed — they are counted on the run, not recorded row by row, because a corpus is mostly misses and listing them would bury the answer.
Excerpt is exactly what pdfgrep printed: the page number, a colon, and the matching line. Only the line is stored — never the document.
⚠ unreadable rows are not misses. They are documents the search could not open, so nothing is known about them either way. If any are listed, the run's answer is incomplete until they are fixed or removed.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (17 steps)
search_id
trim
Trim whitespace from setting search id
id_present
compare
Check if search id has data
id_guard
guard
Stop if id present equals
run
recued-core.document-search.search.get
Get search on document search
run_found
compare
Check if run record id has data
run_guard
guard
Stop if run found equals
search_ref
template
Generate text from a template
hits
recued-core.document-search.hit.search
Search hit on document search
hit_rows
default
Apply default
hit_rows_sorted
sort
Sort by path
matched_rows
filter
Filter by condition
unreadable_rows
filter
Filter by condition
matched_count
count
Count items in matched rows
unreadable_count
count
Count items in unreadable rows
hits_table_rows
map
Extract from each item
hits_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
▼
Output
summary
card
table
hits_table
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
limit
setting
=
100
search id
setting
=
[object Object]
Uses (2 operations)
Pack operation
Get search on document search
recued-core.document-search.search.get
Pack operation
Search hit on document search
recued-core.document-search.hit.search
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
Document Search
read-only
Read: search.get · No approvalRead: hit.search · No approval