Action sheet
Each action opened step by step: dialog turned on, recorded path, a plugin found on a single workstation, owner and review date. Actions without an owner are retired.
Deliverable: ficha_acoes.csv reviewed with the retouching teamOcto for actions and batch processing in Photoshop
Photoshop processes whole folders with recorded actions, through Batch, droplets, the Image Processor and variables. Octo inventories the actions, writes the output profiles and the naming pattern, calls the action from a script with several outputs without overwriting anything and checks the folder by content. The photo, the retouching and the release stay with people.
Six possible deliverables, drawn from the research. None of them saves over the original, all of them check the result by content, and all of them go to review by whoever answers for the image.
Each action opened step by step: dialog turned on, recorded path, a plugin found on a single workstation, owner and review date. Actions without an owner are retired.
Deliverable: ficha_acoes.csv reviewed with the retouching teamWeb, catalog and print, with long side, quality, ICC profile and file size range. The script and the check read the same file.
Deliverable: perfis_saida.json with historyThe action does the retouching; the script decides name, destination and sizes, closes the original without saving and logs each file.
Deliverable: processar_lote.jsx and registro_lote.csvVariables in the template and a data set checked before import: column names, quotes in the price, photo path, file name.
Deliverable: lote_variaveis.csv, checkedJPEG, PNG, TIFF and PSD dimensions, embedded ICC profile, file size, naming pattern, what is missing and what is extra.
Deliverable: conferencia.csv and a manifest with sha256The input folder is read-only; the queue works on copies with sha256, in parts that redo themselves.
Deliverable: fila_lote.sh and fila.csvThe same Octo cycle, applied to actions and batch processing. Each arm has a narrow role; the ones who approve the image, the action and the delivery are people.
Which batches go out every week, with which actions, on which Photoshop version and on how many workstations.
Action sheet, output profiles, naming pattern and data sets in versioned files.
Read-only input, separate output, nothing overwritten, photos of people and spreadsheets with names flagged (LGPD, Brazil's data protection law).
Batch, droplet, Image Processor, variables, script or cloud, depending on the task and the volume.
A script that calls the action, a queue for the input folder and the check, with the source of each rule noted.
Dimensions, ICC profile, file size, names, missing and extra files. "The batch finished" is not a check.
Checked folder and manifest. Delivery to the e-commerce site or the client is approved by a person.
Actions and versions, profiles, who approved each batch and what changed from one version of the action to the next.
Octo closes the original without saving and does not overwrite files. It does not approve photos, does not change actions without review and does not hold anyone's license.
The criteria Octo uses to choose, with the documented limit of each path.
| Task | Path | Notes |
|---|---|---|
| Same action on a folder, one destination | Batch | Action with no dialogs and no recorded path |
| Studio input folder | Droplet with a queue | A droplet keeps the destination from when it was created |
| JPEG for web and TIFF for archive | Image Processor | Options to check in the installed version |
| Several outputs with the client's naming | Script with app.doAction | The script decides name and destination and doesn't overwrite |
| Series of pieces from a spreadsheet | Variables and data sets | Spreadsheet checked before import |
| Turning a reviewed action into code | "Copy As JavaScript" and batchPlay | Developer mode; see the scripts page |
| Large volume without a workstation | Photoshop API, execute-actions | Up to 10 actions and one image per request |
Three steps. Each one only makes sense after the previous one has shown results on your team.
A proposal, not a promise
Octo opens the actions and checks the folder that already goes out, without changing how you process.
Written profiles, a naming pattern and the script calling the reviewed action with several outputs.
Input folder in a checked queue and series of pieces from a checked spreadsheet.
Every point below has a source published by the vendor, by the project or by the responsible agency. The sources are in the next section.
7
points with a published source, each with its reference shown alongside.
batchPlay calls; commands that change the document run in executeAsModal.Source: developer.adobe.com, batchPlay and executeAsModalOcto prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.
Surveys, calculates, organizes and produces the documents: processed files, proofs, reports and spreadsheets.
Deliverable: material ready to checkThe client or the art director checks what Octo delivered before approving. If something doesn't add up, it goes back to Octo with the correction.
Step: checked by the person who approvesOcto does not approve the artwork. Artwork carries no legal signature: approval of the artwork and the proof stays with the client or the art director.
Approval: client or art directorAdobe developer pages (UXP, batchPlay, executeAsModal, manifest, migration, Photoshop API), Photoshop help pages and an Adobe community post, consulted on Oct 31, 2026.
The assessment starts with the sheet of the actions that already run and a check of an output folder that already exists. You get what is missing, what is extra, what fell outside the profile and the questions only your team can answer, and you decide with that in hand.