A flow is a set of connected cards on the visual canvas. The point of a flow is not the one video you made with it. It is that you can change the input and run it again, a hundred times, without rebuilding anything.
This article is about getting to that point.
The pattern that makes a flow reusable
A flow that is worth reusing usually has 2 layers.
A card that writes the prompts. A text card that takes your input, a song, pasted lyrics, a list of topics, and turns it into the specific instructions for each visual: scene 1, scene 2, scene 3, each with its own description.
Visual cards that carry them out. Image or video cards connected to that first card. They do not hold the creative decisions. They take what they are handed and generate it.
The reason this works: when you want a different result, you change one card, not 8. And when you swap the input for a different song, everything downstream adapts on its own.
If instead you write a full prompt into every image card by hand, you have built one video, not a flow. Changing anything means editing every card, and they drift apart.
Let the Agent build the first version
Describe the whole thing to the Visuals Agent in one go, with as much detail as you can. It builds the cards, wires them together, and runs it.
The more you put in the first message, the less you fix later. Worth naming:
How many outputs you want
The aspect ratio
The look, or a reference image to follow
Anything that must be exact: text that should appear as written, a language that must not be translated, a name spelled your way
Any model preference
Example: "Take pasted lyrics as input and make 8 vertical images for a carousel. One card writes all 8 prompts, each with its own text overlay, exactly as written and not translated. Connect it to 8 image cards."
Run the whole thing, or just one card
You rarely need to re-run everything.
Run runs the whole flow.
Run this card re-runs one card.
Run from here re-runs that card and everything downstream of it.
All 3 show the price before they start. If shot 5 came out wrong, fix shot 5. If the prompt writer was wrong, fix that card and run from there.
You can also point the Agent at what broke and it will fix and re-run only those cards.
Nothing is lost when you re-run
Every card keeps its versions, and each version keeps the prompt, model, duration, ratio, quality, and settings that made it. So you can generate 5 takes, click back to the second one, and have the exact recipe that produced it.
To branch off a take without disturbing the card that made it, right click the result and extract it onto the canvas as its own asset card.
Batch: one input, many outputs
The input does not have to be one song. Feed the prompt writer a list, 10 topics, 12 tracks, a set of scenes, and have it produce one prompt per item, then connect that to the cards that generate them.
This is where a flow stops being a shortcut and starts being production. The same structure that makes 1 lyric video makes 40.
Reuse it on the next release
Duplicate the flow from its menu in My Library and change the input. The original stays untouched.
Pin it to the sidebar so it is one click away.
Rename it something you will recognize in 3 months. "Vertical lyric carousel, 8 up" beats "Untitled flow 4".
Share it with a teammate as viewer, editor, or owner.
Keep one good flow rather than making a new one each time. Every new flow is a chance for your prompts to drift. Make small edits to the card that writes the prompts, and save real variants separately.
Each flow also remembers your last choice of model, ratio, duration, quality, and audio, and starts the next blank card there. That memory belongs to the flow and never carries into a different one.
Check the prompts, not just the pictures
When a result is wrong, the fault is usually in the prompt that was written for it, not the model that ran it.
Open the result and read the prompt that was actually sent. Then ask:
Did it carry the exact text you wanted on screen?
Did it say not to translate?
Did it name the language?
Did it keep the constraint you care about, or quietly drop it?
If a constraint went missing, it belongs in the card that writes the prompts, so every future prompt carries it.
Teach it once, permanently
If you find yourself typing the same brief every week, that is a skill. Write it once in Settings, with a clear line describing when it applies, and the Agent reaches for it on its own. Brand rules that apply to everything belong in custom instructions instead.