Use “Review what a set is carrying” in Recued. Show, photo by photo, what a set's images were carrying before they were stripped — GPS coordinates, camera, device serial, capture time. It reads information without changing data in the connected service.
Review what a set is carrying
Use “Review what a set is carrying” in Recued. Show, photo by photo, what a set's images were carrying before they were stripped — GPS coordinates, camera, device serial, capture time. It reads information without changing data in the connected service.
Complete workflow
Job Photo Delivery
7 pinned recipes
Use Job Photo Delivery in Recued for exif, metadata, privacy, and gps. It includes 16 built-in actions and 6 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 photo set” in Recued. Open one delivery set for a customer. The set is keyed on its label, so re-running with the same label converges on the same set rather than opening a second one.
Use “Add a photo to a set” in Recued. Register one inbound file record as a photo in a set.
Use “Prepare a photo for delivery” in Recued. Extract one photo's embedded metadata, record exactly what it was carrying, then produce a metadata-stripped delivery copy and a thumbnail derived from that stripped copy.
Use “Deliver a photo set” in Recued. Mail a set's prepared photos to the customer as attachments.
Use “Show the photo sets” in Recued. List photo sets with their customer, status and photo counts. Read-only — it opens no image and runs no CLI.
Show all 7 recipes
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Reading the disclosure
One row per photo. Had GPS and Where it says it was taken are the ones that matter: a phone photo of a customer's property carries that customer's home coordinates, and every recipient and every mail server in the path would have seen them.
What this tells you is what the ORIGINAL carried. The delivery copy has had all of it removed — that was Prepare a photo's job, and the thumbnail is derived from the stripped copy too, so the preview is clean as well.
⚠ pending photos have no disclosure yet. A photo shows blank fields and Had GPS = false until it has been prepared, and false there means "not examined", not "nothing embedded". The card counts them separately for exactly that reason, and Deliver a photo set refuses while any remain.
⚠ The originals are untouched on your server. Stripping wrote new copies; nothing deleted or overwrote the file you started with. If you need the coordinates later they are still there, and the metadata report record holds a full JSON dump besides.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (24 steps)
set_id
trim
Trim whitespace from setting set id
id_present
compare
Check if set id has data
id_guard
guard
Stop if id present equals
set
?
set_found
compare
Check if set record id has data
set_guard
guard
Stop if set found equals
set_ref
template
Generate text from a template
photos
?
photo_rows
default
Apply default
photo_rows_sorted
sort
Sort by filename
photo_count
count
Count items in photo rows sorted
prepared_rows
filter
Filter by condition
pending_rows
filter
Filter by condition
located_rows
filter
Filter by condition
serial_rows
filter
Filter by condition
prepared_count
count
Count items in prepared rows
pending_count
count
Count items in pending rows
located_count
count
Count items in located rows
serial_count
count
Count items in serial rows
cameras
pluck
Extract camera from each item
unique_cameras
unique
Remove duplicates from
camera_list
join
Join items with ", "
disclosure_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
limit
setting
=
100
set id
setting
=
[object Object]