Use “Look at one person” in Recued. See who a roster entry actually is — their reference photo shown from your own folder, beside the name and address Recued will use for them — so a wrong or duplicated face is something you can see rather than guess at.
Look at one person
Use “Look at one person” in Recued. See who a roster entry actually is — their reference photo shown from your own folder, beside the name and address Recued will use for them — so a wrong or duplicated face is something you can see rather than guess at.
Complete workflow
Photo Attribution
16 pinned recipes
Use Photo Attribution in Recued to match one event's photos to the people you know, write a warm line for each picture, review them, and send everyone their own. Faces are matched on your machine; your photos are never copied; sending asks first. First install two programs on the server: face_recognition (pipx) and libvips (brew install vips). Then allow their actions on each tool pack's Access tab. Open “Scan an event folder” for the rest of the setup.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Scan an event folder” in Recued. Compare every photo in one event folder against the people you know, and record who appears in each picture. Photos stay where they are and are never copied. Matching happens on your own machine.
Use “Write the photo lines” in Recued. Look at each scanned photo and write one warm line naming the people recognised in it. A small copy with its embedded details removed is what the model sees, and the original is never sent. Run it again until the queue is empty.
Use “The roster” in Recued. See everyone Recued can recognise, whether each person can actually be written to, and who has been retired — and open any of them from here, which is the only way in to a person.
Use “Review photos before sending” in Recued. List the photos waiting for a look, with the line that will arrive alongside each one and the names it was written for. Open a photo to approve it, rewrite the line, or leave it out.
Use “Review one photo” in Recued. See the picture itself beside the names Recued matched in it, correct the line it wrote, and say whether it is ready to send — the one place a wrong name or a wrong sentence can be caught before it reaches somebody.
Show all 16 recipes
Use “Set someone's details” in Recued. Fill in an email address and the name that messages should use for one person on your roster. A field left blank keeps what is already there rather than clearing it. The key derived from their reference photo cannot be changed.
Use “Retire a person” in Recued. Take somebody off the roster without deleting anything they are attached to — a duplicate left behind by a renamed reference photo, or someone who should not be sent to any more. Their photos stay on record; they simply stop being matched and stop being sent to.
Use “Import the roster (CSV)” in Recued. Add everyone to the roster from a spreadsheet in one go — their key, the name messages should use, and their email address — instead of typing each person in after the first scan.
Use “Export the roster (CSV)” in Recued. Copy out everyone on the roster as a spreadsheet, or - on an empty roster - get the column headings the importer expects, so you can fill them in and import the list instead of typing it.
Use “See who is ready to receive” in Recued. List everyone with approved photos waiting, and separately everyone recognised who has no email address yet. Send each person from here. Nobody is dropped quietly, because a missing address is the usual reason a photo never arrives.
Use “Re-describe a person” in Recued. After changing someone's name, rebuild the stored names on their photos and queue those photos to be written again. Photos already approved are left alone and counted, because somebody signed those off.
Use “Skip a photo” in Recued. Leave one photo out of the sending queue and release everyone who was waiting on it. Their other photos are untouched, so this cancels one picture for everyone in it rather than cancelling a person.
Use “Send one person their photos” in Recued. Send one person a single message carrying every photo of them that has been approved. A fresh copy of each picture is made with its embedded details removed, and that copy is what travels.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Use “See what has been delivered” in Recued. Show who has received which photo and when, one row per person per picture, with the message it arrived under. It reads information without changing anything.
What this does
Shows one person on your roster: their reference photo, the name messages will use, and the address they will go to.
The photo is read live, never copied
The picture comes straight from your roster folder each time you open this. Recued keeps no copy of it, so swapping in a better photo of somebody changes what you see here immediately — there is nothing to refresh and nothing to tidy up.
That also means the photo disappears from here if you move or rename the file, which is the honest signal: the roster entry is now pointing at a file that is gone, and the next scan will not match that person either.
Why look at all
The file name decides who somebody is. Nothing else checks that 001 - Maggie Chen.jpg actually holds Maggie, so this is the only place a wrong reference photo shows up before it sends somebody else's pictures to her.
It is also how you spot the same face saved twice under two keys — two entries, one person, and both would be sent to.
When there is no photo
Somebody added before this pack recorded reference file names has nothing to look at yet, and so does somebody whose file has moved. Re-run Scan a folder on their event and the entry is refreshed.
When their name was wrong
Write their photo lines again throws away the line on each of their photos that is still waiting and writes a fresh one — which is what you want after correcting a name, because every line naming them says the old one.
Photos you have already marked ready are left alone, so anything you have signed off keeps its wording. If you have corrected a line by hand and want to keep it, mark that photo ready before doing this.
Why they were retired
Retiring somebody asks for a reason, and this is where it is kept. Months later "why is this person not in any of these photos" is a question only that sentence answers.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (18 steps)
profile
recued-core.photo-attribution.face_profile.get
Get face profile on photo attribution
found
compare
Check if profile record id has data
guard
guard
Stop if found equals
stem
trim
Trim whitespace from profile record reference stem
folder
trim
Trim whitespace from profile record reference folder
can_look
all
Check if all conditions are true
candidates
default
Apply default
tries
recued-core.photo-derive.image.preview
Preview image on photo derive
skip: step.can_look equal false
hits
filter
Filter by condition
hit_n
count
Count items in hits
has_image
compare
Check if hit n is greater than 0
read
core.storage.file.read-temp
Read temp storage file
skip: step.has_image equal false
live
default
Apply default
skip: step.has_image equal false
photo_note
ternary
Apply ternary
actions
default
Apply default
is_retired
compare
Check if profile record status equals retired
retired_note
ternary
Apply ternary
card
to_summary
Format results as a summary card
▼
Output
summary
card
file_preview
live
record_fields
profile.record
button
actions
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
profile id
setting
=
[object Object]
Uses (3 operations)
Pack operation
Get face profile on photo attribution
recued-core.photo-attribution.face_profile.get
Pack operation
Preview image on photo derive
recued-core.photo-derive.image.preview
Files
Read temp storage file
core.storage.file.read-temp
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
Photo Attribution
read-only
Read: face_profile.get · No approval
Read
Files
core.storage.file.read-temp
read-only
1 more isn't listed here. You'll see it at install.