Use “Add a photo to a set” in Recued. Register one inbound file record as a photo in a set.
Add a photo to a set
Use “Add a photo to a set” in Recued. Register one inbound file record as a photo in a set.
Complete workflow
Job Photo Delivery
8 pinned recipes
Use Job Photo Delivery in Recued for exif, metadata, privacy, and gps. It includes 16 built-in actions and 7 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 “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 “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.
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 8 recipes
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Use “One photo” in Recued. Open one photo from the list that names it, and read everything recorded about that photo on one page.
Adding a photo
Take the file record id of a photo already in data.file.received — a phone upload, a mail attachment, a webclient upload — and register it against a set.
⛔ You choose which photo goes in. This recipe is deliberately manual and takes an explicit record id. A reactive "any new image joins the open set" trigger would be wrong here for the same reason it is wrong in client-document-intake: the file event fires for every inbound file and the record carries no readable origin, so nothing can tell a customer's job photo from a personal one. Auto-enrolling would eventually put the wrong picture in someone's delivery.
⚠ Only images are accepted. The MIME type is checked and a non-image is refused rather than registered — the pack's whole contract is about image metadata, and a PDF that reached Prepare would get ExifTool's PDF path, whose stripping is reversible (ExifTool documents old objects as recoverable). Refusing early is the honest boundary.
Status starts pending and stays there until Prepare a photo runs. A pending photo is never delivered.
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
record_id
trim
Trim whitespace from setting record id
inputs_valid
all
Check if all conditions are true
inputs_guard
guard
Stop if inputs valid equals
set
recued-core.job-photo-delivery.photo_set.get
Get photo set on job photo delivery
set_found
compare
Check if set record id has data
set_guard
guard
Stop if set found equals
set_open
compare
Check if set record status does not equal delivered
set_open_guard
guard
Stop if set open equals
file_meta
core.storage.data-file-read
Data file read storage
defaults
defaults
Apply defaults
is_image
starts_with
Check if mime type starts with image/
image_guard
guard
Stop if is image equals
set_ref
template
Generate text from a template
existing
recued-core.job-photo-delivery.photo.search
Search photo on job photo delivery
existing_rows
default
Apply default
existing_count
count
Count items in existing rows
photo_exists
compare
Check if existing count is greater than 0
photo_create
recued-core.job-photo-delivery.photo.create
Create photo on job photo delivery
skip: step.photo_exists equal true
photo_id
coalesce
Use the first available value from: photo create record id, existing rows 0 id
photo_recorded
compare
Check if photo id has data
photo_guard
guard
Stop if photo recorded equals
set_total
recued-core.job-photo-delivery.photo.count
Count photo on job photo delivery
card
to_summary
Format results as a summary card
▼
Output
summary
card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
set id
setting
=
[object Object]
record id
setting
=
[object Object]
Uses (5 operations)
Pack operation
Get photo set on job photo delivery
recued-core.job-photo-delivery.photo_set.get
Files
Data file read storage
core.storage.data-file-read
Pack operation
Search photo on job photo delivery
recued-core.job-photo-delivery.photo.search
Pack operation
Create photo on job photo delivery
recued-core.job-photo-delivery.photo.create
Pack operation
Count photo on job photo delivery
recued-core.job-photo-delivery.photo.count
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
Write
Pack
Job Photo Delivery
external change
Read: photo_set.get · No approvalRead: photo.search · No approvalWrite: photo.create · No approvalRead: photo.count · No approval
Read
Files
core.storage.data-file-read
read-only