Skip to content
Ajay B J

Case study · AI & Content · Business & Product

Ajay AutoFlow

Chrome extension that batch-runs Google Flow prompts and saves every clip in order

A Chrome extension for AI video creators: paste or import a whole storyboard, press Start, and it runs every scene in Google Flow, picks the right character and voice, and saves each clip with a timecoded file name. It also has pause/resume with crash recovery, a run report with retry-failed, and a companion website with a storyboard planner.

Open AutoFlow websiteFree downloadCode on GitHub
Status
LiveFree download · install from ZIP (not on the Chrome Web Store yet)
My contribution
Built it for my own AI video work: I mapped the manual routine in Flow, decided what to automate and what to leave out, designed the side panel and website, and tested each feature.
Tools
JavaScriptChrome Extensions (Manifest V3)Side Panel APIChrome DevTools Protocolchrome.storage / downloads / notificationsHTML & CSSVercelGitHub
How AI was used
Code was generated and refactored with Claude (Claude Code). I defined the workflow, reviewed the changes, and tested the extension and website myself.

The problem

A single AI video in Google Flow can need 30 or more scenes. Every scene was the same routine: paste the prompt, choose the character and voice, set the model and ratio, click Generate, wait, download, then rename the file to its timecode so the editor gets them in order. That's roughly 150 clicks for one video, and files easily end up mixed up.

What I built

  • A side-panel Chrome extension that runs a queue of prompts in Flow one after another (text to video, frames to video, ingredients, text to image, image editing)
  • Character and voice picking by name, plus per-prompt settings lines (voice, model, ratio) at the top of a prompt
  • Scene import from Google Sheets or CSV, with templates like {character} {action}, cinematic
  • Timecoded file names (#0:04 → 0-04.mp4), a sub-folder per project and optional caption files
  • Pause and resume, and crash recovery that continues an interrupted batch where it stopped
  • A run report with time per scene, 'Retry failed only' and a CSV shot list, plus a live time-left estimate and a done notification
  • A self-check that shows which Flow controls it can still find after a Google update, and an English / Hinglish panel
  • A companion website with the download, install guide and a storyboard planner that exports straight into the extension

Workflow

From storyboard to a folder of finished clips

  1. 1Plan

    • Storyboard planner (web)
    • Google Sheets / CSV
    • Prompt templates
    • Per-scene voice, model, ratio

  2. 2Side panel

    • Prompt queue
    • Projects & settings
    • Pause / resume
    • Time-left estimate

  3. 3In the Flow tab

    • Types each prompt
    • Picks @character + voice
    • Generates & waits
    • Downloads at chosen quality

  4. 4Output

    • Timecoded files (0-04.mp4)
    • Folder per project
    • Caption .txt files
    • Run report + CSV shot list

Screenshots

  • Website with a download button and a preview of the side panel mid-run

  • What the extension does

  • Storyboard planner: plan scenes on any device, then export a CSV the extension imports

Decisions I made

  • Kept it an extension, not a web app: only an extension can act inside your own signed-in Flow tab; a server would need people's Google logins
  • No servers and no tracking: everything runs in the user's browser and talks only to Google Flow
  • Left out anything that gets around Flow's plan limits, credits or watermarks
  • Built to survive redesigns: controls are found by text, labels and icons, with editable selectors and a self-check

Where it stands, honestly

AutoFlow is a free download from its website and the code is public on GitHub. It's installed by loading the unpacked folder; it isn't on the Chrome Web Store yet. Because it drives Google Flow's interface, a Flow redesign can break a step until the selectors are updated. It has no user numbers to report yet.

What I learned

  • Automating someone else's interface means planning for change: fallbacks, logs and a self-check matter as much as the happy path
  • Long-running jobs need recovery: pause, resume and 'retry failed only' turned a fragile script into something I can leave running
  • A small website and a clear README make a tool much easier to share than a ZIP file on its own