Make your FLORA workflows scale with Batch Nodes

FLORA was built for creative exploration. The problem is that the best ideas eventually need to ship, and shipping usually means volume. Thirty campaign variants. A hundred product colorways. An entire client library, restyled to match a new brand direction.

Batch Node closes the gap between an idea and all the variations you need shipped. Connect your assets into a single node, wire it into your existing workflow, and run everything at once.

Here are three ways to put Batch Node to work.

Try-on shots at scale 

The use case: you have a model shot and a set of clothing or product items you want to see on that model. Without Batch Node, you're uploading each item individually and running the workflow one by one.

With Batch Node, you add all your items into a single Batch, connect it to your try-on workflow, and run. Each item gets processed individually through the same generation pipeline — consistent model, consistent lighting, consistent output quality — and you end up with a full set of try-on shots in a single pass.

How to set it up:

• Add a Batch Node to your canvas from the Add Node menu

• Upload your clothing or product images into the Batch (or connect them from existing nodes on your canvas)

• Connect the Batch to your image generation node with your model reference and prompt

• FLORA processes one output per item in the Batch

Product mockups across multiple backgrounds 

The use case: you have one product shot and you want to see it placed in 10 different environments (lifestyle settings, studio backgrounds, outdoor scenes, etc). This is the kind of work that used to mean either a full shoot budget or a very long afternoon.

With Batch Node, you build your product mockup workflow once, drop your background references into a Batch, and let it run. You get back a full set of mockups, each with the same product placed consistently across every scene.

How to set it up:

• Build your product placement workflow on the canvas (product image node → generation node with your prompt)

• Add a Batch Node and upload your background reference images

• Connect the Batch into your generation node alongside the product image

• Each background gets its own output with the product placed correctly

Style replication from a reference 

The use case: you have a style guide or a reference image that defines a look — a specific color treatment, a photographic style, a visual tone — and you want to apply it consistently across a full asset library.

This is where Batch Node changes the equation most dramatically for brand and agency teams. You define the style once through your reference, connect your asset library to a Batch, and run everything through the same generation node. Every output reflects the same visual direction, without you touching each asset individually.

How to set it up:

• Connect your style reference image to your generation node

• Add a Batch Node and upload the assets you want restyled

• Wire the Batch into the generation node as the content input

• Refine your prompt until the style transfer looks right on one asset, and then run the full Batch

A note on getting the most out of Batch Node

Before you run a large batch, we recommend first testing your workflow on a single asset. Make sure the input-to-output transformation is exactly what you want, which means getting your prompt dialed in and ensuring your reference is working correctly before you scale it up. Once you're happy with one output, Batch Node will give you that same result across everything in your set. Currently, Batch Node only supports one output node, but full output workflows are coming soon.

Open your canvas and try it today. Read more in FLORA Docs.