CONTENT CREATION

Generate hero images from a product CSV drop in Google Drive

Watches a Google Drive folder for a new product export CSV, generates a hero image per row with the built-in image generator.

CategoryContent Creation
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew product CSV appears in watched Google Drive folderGoogle DriveGoogle Drive
  • LogicParse CSV into per-product rows
  • ActionGenerate a hero image per rowImage generation
  • LogicBrand-consistency check; drop off-brand renders
  • OutputWrite approved assets + manifest CSV to Google DriveGoogle DriveGoogle Drive

What it does

Lets a non-technical operator kick off a whole image batch just by dropping a CSV. When a new product export appears in a watched Drive folder, the flow parses each row, generates a hero image, checks it against brand rules, and returns the assets alongside a manifest mapping each SKU to its image.

When to use it

Use it when product data comes out of another system as a spreadsheet export and you do not want to wire up an API. Perfect for merchandisers who already work in Drive and need a fast, repeatable way to produce hero art for a launch or a seasonal refresh.

How it works

  1. 1A new CSV landing in the watched Google Drive folder triggers the run.
  2. 2The CSV is parsed into product rows with name, category, and color fields.
  3. 3For each row a hero prompt is built and rendered with the image generator.
  4. 4A brand-consistency check filters out renders that miss palette or framing rules.
  5. 5Approved images are written to a dated output folder in Google Drive.
  6. 6A manifest CSV mapping SKU to image link and review status is saved beside them.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect Image generationManaged Nano Banana image renders, metered per image.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.