NiceCodeAutomation Labs — Auto Flow: batch image & video generation done for you
Paste your prompt list, hit run. The extension types into the real prompt box, tags @ characters, clicks Generate, tracks every result tile and downloads images/videos with the right filenames — right in the Flow tab you're signed in to.
Install from Chrome Web StoreSee pricing
Free: 20 jobs/dayChrome 114+, runs in the side panelNo API keys, no private API calls
How it works
Four steps, no technical skills needed.
Install the extension, open Flow
Install from the Chrome Web Store, sign in to labs.google and open a Flow project. Click the extension icon and the app opens in the browser's side panel.
Check the page elements
The UI Control tab auto-detects the prompt box, Generate button and Characters tab. If it picks wrong, point and click the right element — the extension remembers it next time.
Paste prompts, tag characters
One prompt per line, or import a .txt/.csv. Scan characters from Flow and choose how each one gets @-tagged: per prompt, on every prompt, or by index.
Run and let it work
The queue runs sequentially, tracks the real progress of every result tile and downloads when done. A status light warns you the moment the Flow tab is closed.
Built to run hundreds of jobs reliably
Every feature is verified against the real Flow UI, not a demo.
Batch queue
Queue hundreds of prompts to run one after another; duplicates and blank lines are skipped, with random pauses between jobs. Pause, retry or delete any job.
Characters (@ mention)
Scans the characters in your project and @-tags them exactly like typing by hand. Three tagging modes per character, plus JSON scene config when you have many characters.
Real result tracking
Locks onto the result tiles of each submission: reads the progress %, the media or the error message right in the tile. Failed jobs show Flow's reason verbatim.
Auto-download resultsPro
Downloads a job's images/videos the moment it finishes — one file per result tile, with duplicate protection across jobs. Download everything or just the selected items.
Filename templates, .txt/.csv importPro
Name files from a template with the job index, import prompt lists from a file, save presets, export/import your config to another machine.
Project libraryPro
Browse your Flow projects and media inside the extension, bulk-download a whole library, re-download with new names after changing the template.
Self-detecting UI control
Finds the prompt box, Generate button and Characters tab on its own. When Flow changes its UI, point and click to reselect or receive updated selectors from the server.
Errors that tell you what to do
Every failed job comes with a full report: which step it stopped at, the element in use, the result, plus what to do next. A Diagnose page button helps when Flow changes.
Safe by design
Only does what you could do by hand. Flow builds its own requests and attaches reCAPTCHA itself; the extension never guesses payloads or mints tokens.
Drives the UI, never calls the API
The approach determines the reliability. These are deliberate choices — and their trade-offs.
Real typing, real clicks
Tools that call Google's private API keep breaking because the payload can change at any time. Auto Flow guesses nothing: the prompt is typed into the real prompt box, the real Generate button is clicked, and Flow handles the rest. Model, aspect ratio and images per generation follow whatever you've set on the page.
Clicks that look human
Flow ignores clicks generated by JavaScript. The extension sends mouse and keyboard events at the browser level via the DevTools Protocol, so the page can't tell them apart from a real hand. There's always a random pause between two jobs.
Your data stays on your machine
Prompts, images, videos and projects never reach NiceCode's servers. The server only stores your encrypted email and the number of jobs used today for the daily quota.
The trade-off you should know
Chrome shows a yellow bar reading "Automation Labs is debugging this browser" on the Flow tab while the queue runs. It can't be turned off. Don't click Cancel on that bar and don't open DevTools on the Flow tab while running, or the extension loses the ability to click.
The extension uses your own Google session and Flow credits. Automating Google Labs may violate Google's terms — weigh that against your own account.
Requirements
Chrome 114 or newer (side panel), a Google account with access to Google Flow, and an open Flow project. Works on Windows, macOS and Linux.
Free to try it out, Pro for volume
Batch runs, UI control and characters are always free. Pro removes the job limit and unlocks output automation. Compare in detail.
Pro Monthly
Flexible, month to month
25.000 ₫$3.00 / 30 days
- Unlimited extension jobs
- Auto-download, bulk download, project library
- Presets, filename templates, .txt/.csv import
- +60 Scene Studio credits every month (≈ 1 h of video)
- Up to 3 devices, cancel anytime
Pro Quarterly
One payment for 3 months
69.000 ₫$7.00 / 90 days
≈ 23.000 ₫/month save 8%≈ $2.33/month save 22%
- Everything in Pro Monthly
- +70 Scene Studio credits every month (≈ 1.5 h of video)
- No monthly renewals
- Keep access until the paid period ends, even if you cancel
Pro Yearly
Best value for regular users
249.000 ₫$30.00 / 365 days
Only ≈ 20.750 ₫/month instead of 25.000 ₫Only ≈ $2.50/month instead of $3.00
- Everything in Pro Monthly
- +90 Scene Studio credits every month (≈ 1.5 h of video)
- One payment for the whole year
- Keep access until the paid period ends, even if you cancel
Auto Flow FAQ
Does the extension need an API key or a separate Google account?
No. It runs right in the Google Flow tab you're signed in to and uses your own Flow credits. You only sign in to NiceCode with your email for the daily quota and Pro features.
Why does Chrome show a yellow "is debugging this browser" bar?
Google Flow ignores every click generated by JavaScript. To press Generate like a human, the extension sends mouse and keyboard events at the browser level via chrome.debugger, and Chrome always shows that yellow bar when a debugger is attached to a tab. It can't be hidden. Don't click Cancel on the bar while the queue is running and don't open DevTools on the Flow tab.
Will the extension break when Flow changes its UI?
The extension detects elements (prompt box, Generate button, Characters tab) using several signals and receives selector updates from the server when Flow changes: Pro gets the early channel, Free gets the delayed channel a few hours later. If something is still off, point and click the right element in the UI Control tab — no need to wait for an update.
Where do I pick the model, aspect ratio and images per generation?
Set them once on the Flow page as usual. The extension never touches those settings; every job in the queue uses exactly what you've set.
Do failed jobs count against my quota?
Jobs that fail before reaching Flow (element not found, cancelled midway) are refunded to your quota automatically. Jobs Flow rejects for content policy stop immediately and aren't retried, so your Flow credits aren't wasted.
Can I run several jobs in parallel?
No. A Flow tab has a single prompt box, so the queue runs sequentially with a random pause between jobs to look human. The Flow tab doesn't have to be in the foreground, but don't close it.
Install free, run your first job in 5 minutes
20 jobs/day, no card required. Upgrade to Pro inside the extension when you need more.