Trigger-file driven image resizer. When a new image lands in an inbound folder, generates thumbnail and web-size variants and moves the original to a processed folder.

`image-batch-resizer`

Trigger-file driven. When a new image lands in an inbound folder, generates thumbnail (200px), web (1024px), and hd (2048px) variants, then moves the original to an archive subfolder.

Use case

Photo workflow automation: photographers drop files into one folder, downstream apps pick up the right size from the right subfolder. No manual resizing, no Photoshop batch.

This is a YAML workflow, not a skill — convert is the tool, no AI involved.

Setup

Install ImageMagick on the InTouch host (apt install imagemagick / brew install imagemagick)
Create a trigger-file watching your inbound folder, e.g. /data/uploads
Link the trigger to this workflow
The workflow fires per file landing; the trigger engine sets TRIGGER_FILE to the file path

Pipeline

resize — runtimeenv (bash + ImageMagick convert) — three resize calls plus an mv to archive

Folder layout after a run

/data/uploads/
  originals/    <- the original full-res file is moved here
  thumb/        <- 200x200 cap
  web/          <- 1024x1024 cap
  hd/           <- 2048x2048 cap

The > modifier on -resize means "shrink only" — files smaller than the target dimension are passed through unchanged.

Customization

Sizes — edit the three convert lines for your dimensions
Format conversion — append .jpg to the output filename to force JPEG (${STEM}.jpg)
Quality — bump the -quality value for less aggressive compression
Per-file routing — branch on EXT if you want different processing for .png vs .jpg

Source

See workflow.yaml.