Process nested photo or record batches one item at a time

Breaks large batches of nested records or images into single items so each one processes without errors.

How the work actually flows

It repeats. Repeats for remaining items; runs once per each nested record or image.

Pattern: Multiple Instances without Synchronization (12) ยท Structured Loop (21)

flowchart TD trig[\"nested batch received"\]:::trigdata s0["split batch into individual items"]:::task s1[["process each item"]]:::mi s2["check if items remain"]:::task s3["flattened set ready"]:::task trig --> s0 s0 -->|"one per each nested record or image"| s1 s1 --> s2 lp{"all nested items processed"}:::gate s2 --> lp lp -. "repeats for remaining items" .-> s1 lp -->|"finished"| s3 out[/"fully processed flattened item set"/]:::out pay{{"no skipped or duplicated items"}}:::pay s3 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepRuns once per itemRepeat or finishResultPayoff
Build size
Standard

A mid-size build with several tools working together.

Business functions
Image & Media Processing
Connects
Google SheetsGoogle Drive

The problem it solves

When you're processing lists that contain lists inside them, like orders with multiple line items or folders full of images, doing it one by one by hand is slow and error-prone. Batch tools that choke on nested data can silently skip or duplicate items.

Who it fits

Operations or data teams handling large batches of nested records, files, or images.

How it works

  1. A batch of nested records or images is received
  2. Each item is split out into its own individual entry
  3. Every single item is processed in turn
  4. The system loops until every nested item has been handled
  5. A clean, flattened set of processed items is ready for the next step
What you get

Batches flattened into clean single items

You get large nested batches of records or images broken down into clean individual items ready for the next step.

What you get

A complete set of individually processed records or images with nothing skipped or duplicated.

What you need

Whatever storage or spreadsheet system holds your source data, such as Google Sheets or Google Drive.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook