Chrome extension · Google Flow
Auto Flow works through a whole batch inside your own signed-in Flow tab — entering each prompt, waiting for the result, downloading it and filing it under a name you can search. Veo 3.1 and Nano Banana, video and image.
Free version: 10 prompts per batch, results stay in Flow for you to save. No account, no card, no trial timer.
| No. | Prompt | Progress |
|---|
Per prompt
Back to the project's base URL before every item. Flow's single-clip editor looks identical and silently never generates — this is what stops a batch dying at item two.
Confirms the text actually landed in the box before clicking, and reports what it found if it didn't.
Not "something appeared" — this card, tracked through completion, because a finished clip drops its caption and a busy project is full of other people's thumbnails.
1K or 2K for images, 270p to 1080p for video. If a clip doesn't offer your choice, it takes what's there and says so rather than stalling.
Flow's own filename is compared against the prompt, duplicate results are refused, and a grid thumbnail is never mistaken for an opened result. A wrong file saved under the right name is worse than a failed item — so it fails the item.
Pricing
Needs Chrome, and your own Google Flow account with credits — Auto Flow runs bulk prompts through Flow, it does not include Flow access. It never handles your Google sign-in: it works inside the tab you are already signed into.
Honestly
Worth knowing before you pay, not after.
Auto Flow drives Google's interface. When Google redesigns something, the affected step stops working until it's fixed. Every failure prints what it found on the page, which is what makes those fixes quick — but the risk is real, and it's why this is billed monthly rather than sold outright.
You bring your own Google Flow account. Video generation consumes credits; when they run out the batch stops and leaves the rest Pending, so nothing is lost.
Chrome suspends idle extensions after about 30 seconds. The open panel holds the connection that prevents it. Close it mid-run and the batch stops.
It drives that exact tab, so browsing your media library in it mid-run pulls the page out from under the current item. Use a second window.
The queue is strictly sequential. Running several in parallel would race Flow's own interface against itself.
Firefox's stricter automation handling and Google's sign-in checks made it unworkable there. Edge and Brave should work; they're untested.
Questions
Into a subfolder of whatever Chrome's download location is set to. Point
Chrome at any drive and everything follows — that's how results end up outside
C: without the extension needing special permission.
Flow names each download after what it actually sent, so that name is checked against your prompt. Results are told apart by their image URL, and a name Flow has already used in this run is refused — every prompt in a batch is different, so a repeat means a stale result.
Yes. Untick auto-download and prompts still run with every setting applied, leaving the results in Flow to pick through by hand.
No. It uses the Flow tab you're already signed into and never sees credentials. That's also why Google's bot detection isn't a factor — it's an ordinary browser session with an extra panel.
Pro stops at the end of the period you paid for and the extension drops back to the free limits. Nothing is deleted — your queue, settings and downloaded files are untouched.
Send the log line. Every step reports the control it couldn't find and lists what was actually on the page, which is usually enough to fix it the same day.
Privacy
Auto Flow is a local tool. There is no Auto Flow server, no account to create, and no analytics of any kind.
flow.google.com, to operate the page on your
behalf, and api.polar.sh, for that licence check. Nothing else is
requested.Uninstall the extension and everything it stored goes with it.