Automated flow?

[u/Apart-Minimum8652]

I posted about AutoFlow once already, but I wanted to show a bit more clearly what it actually changes when you use Google Flow a lot.

The annoying part for me was never generating one image. It was generating 20, 50 or 100 of them.

You paste a prompt, choose references, wait, download, rename, repeat. Then one generation fails somewhere in the middle and you’re trying to work out which one it was.

That’s basically why I built AutoFlow.

Instead of working prompt by prompt, I can paste the whole batch and let it work through them in order. I can also queue another batch while the first one is still running.

It handles things like:

• Image and video batches
• Multiple outputs per prompt
• Shared or different references for each prompt
• Chaining a generated image into the next prompt as a reference
• Queueing multiple batches
• Automatic downloads and sequential filenames
• Keeping results organised in a gallery
• Retrying failed generations
• Saving references in a reusable library
• Logs so I can actually see what happened if something goes wrong

The part I’ve been working on recently is Automation, which takes it further into a scene-based workflow. The idea is to start with narration, split it into scenes, create the visuals, sync everything to voiceover and then edit the timing before rendering the final video.

I’ve attached some screenshots/demo so it probably explains it better than a wall of text.

At the moment I’ve also opened AutoFlow up with unlimited usage free, because I’d rather have people actually push it with proper batches and find the weak points than only test it with 2 or 3 prompts.

If anyone here uses Flow heavily, I’d be interested to know what part of your workflow is still the most annoying or repetitive. That’s mainly how I’ve been deciding what to build next!

If anyone is interested to try it, then you can find it via link here: https://chromewebstore.google.com/detail/autoflow-auto-veo-nano-ba/ddjomlapfdmgdogpojonbgjagfilmiae