Custom workflows

A workflow is a line of steps laid out left to right in the order they run. Drag a folder in, put the steps on the line, and the house works through every piece. Drag to reorder. Open any step to change its settings.

Custom workflows →

The canonical example

Import a folder of shirts. Enlarge the sleeves with the fit step. Add a red variation and a grey variation of each shirt, except where a shirt is already red or grey, which the house works out per item and tells you it is skipping. Upscale every variation to 4K. Compress to a 90% JPEG.

Five steps on one line, and no scripting.

Per-item judgement

The line is not a blind loop. Each step reads the piece in front of it and can skip itself, and when it does it says so on the node rather than quietly doing nothing. A step that will fan out, a recolour producing three variants, shows that it will before you run it.

Cost before you commit

The whole line is totalled before it starts, broken down by step, at the resolution you chose, with the skipped frames already deducted. What is shown is what settles. See quality and cost.

Presets

Save a line as a preset and it becomes a one-click treatment for the next delivery. A preset with no folder bound to it is the shape you run a whole collection against overnight.

Presets and runs are both addressable from outside, under /api/toolkit/pipelines, so an agent can hold your house treatment and apply it to a delivery the moment it lands. See the API.

Related

• The surface that watches them run: the Darkroom.
• Getting the folder in order first: Collections.