Batch Run and triggers

A workflow that gives you one good result can give you fifty. The Automation group holds the nodes that repeat a workflow without rebuilding it: Batch Run loops a branch over a list of pictures, the Run node fires a whole chain from one button, and the triggers start a run on a clock or from a Telegram chat.

None of these nodes generate anything themselves. Each one starts the generators wired to it, and every generation they cause is an ordinary run: it is checked, priced and charged the same way as a press on a node's own Run button.

Image Bulk

Holds up to 50 pictures as one value. Fill it by uploading, or by wiring any image output into Add image. It has two output ports that carry the same pictures with opposite meanings.

Batch Run

Takes the list on its Items port and runs everything wired to its Each item trigger once per picture. It produces nothing of its own.

Bulk Output

Collects every result a batch produces in one grid, grouped under the picture that produced it, filling in as each generation lands.

1. 1

   Add Image Bulk and fill it

   Upload the pictures or wire them in. The counter shows how many are ready out of 50.
2. 2

   Wire One by one into Batch Run

   Connect Image Bulk's One by one port to the Items port of a Batch Run node.
3. 3

   Wire Each item into your generators

   Connect Batch Run's Each item trigger to the first generator of the branch. Chain further nodes behind it as usual; the whole branch runs per item.
4. 4

   Add a Bulk Output

   Wire it to the batch so the results have somewhere to collect. It is also where you download them.
5. 5

   Check the matrix and the price

   The grid on the Batch Run node shows one square per generation the run will buy. The button quotes the full price: every node in the branch, with its own settings, times the items in range.
6. 6

   Press Run

   Items run four at a time. Squares turn purple while working, green when done and red when failed. You can leave the page; results keep arriving.

The Each item wire carries the order of the loop, and the current picture is handed to the nodes wired directly to it. Nodes further down the branch receive what their own upstream produces, exactly as in a normal run. Where the picture lands depends on the node that receives it:

Image Generate and the image tools

The item becomes a reference in the node's attachment strip, beside anything else wired or uploaded there.

Model Generator

The item fills one section you choose on the node, wardrobe by default, so fifty garments can be shown on the same model. A section that is both batch-filled and wired is refused as ambiguous.

Motion Control

The item is the character to animate, so one motion is applied to every picture in the set.

Video Generate

The item arrives on Attachments and takes the active tab's role: a reference, or the start frame.

All

Every picture in the set, in order. The default.

Subset

A range by position, such as items 1 to 10. Useful for a test pass before committing to the whole catalog.

Failed

Only the pictures whose generations failed last time. Successful results are kept and not paid for again.

The matrix and the price on the button follow the range, so what you approve is what runs and what is charged. One square is one database row and one charge; nothing in the grid is decorative.

Bulk Output stores nothing itself. It is pinned to the batch it belongs to and draws every tile live from the run, which is why the results survive a refresh, a closed tab, and even the wire being removed.

It accumulates. Every run of the same batch stacks on top, newest first, and running again never removes what an earlier run made. For a fresh gallery, unwire the node and add a new one. Bulk Output has no output port yet; download from it, or wire individual results onward from the previews.

Wire the Run node's trigger into one or more generators and press it once: everything wired fires as a single ordered run, and the button quotes the total cost of every node the press will charge. Use it when a workflow has several entry points that should always start together.

Run Auto

Each node runs with its own run mode setting. The sticky default, set from the chevron.

Run

Overrides every node to add results for this press only.

Run Overwrite

Overrides every node to replace its wired previews for this press only.

Schedule Trigger fires the nodes wired to it at a time you set, without anyone pressing anything. It offers four cadences, all in the timezone the node picks up from your browser:

Every N minutes

An interval, never shorter than five minutes.

Daily

Once a day at a time you choose.

Weekly

Once a week on a weekday and time you choose.

Custom cron

A five-field cron expression for anything else, with the same five-minute floor.

1. 1

   Wire the trigger

   Connect Schedule Trigger's Trigger port to the first node of each chain it should start.
2. 2

   Set the cadence

   Pick a mode and its time. The node shows the next fire time before you switch it on.
3. 3

   Switch it on

   The Active switch creates the schedule on the server. The node then shows the next and the last fire, and any failures.

The Telegram pair turns a chat into a remote control. Photos and text you send to your bot land in the wired inputs, a trigger word starts the run, and Telegram Send delivers the results back to the chat.

1. 1

   Create a bot

   In Telegram, ask BotFather for a new bot and copy its token.
2. 2

   Connect it on the node

   Paste the token into Telegram Trigger. It is encrypted on the server and never stored in the workflow itself.
3. 3

   Pair your chat

   Scan the QR code or open the link the node shows, then press Start in the chat. The panel disappears once the chat is proven to be yours.
4. 4

   Wire the outputs

   Image into an Image Input, Video into a Video Input, Text and Prompt into Text Inputs, and the Run trigger into your generators.
5. 5

   Send and run

   Anything you send to the bot mirrors into the wired holders live. Sending the trigger word, /run by default, fires the wired chains and nothing else.

Auto Send

Wire results into Telegram Send's Auto Send port and they are delivered to the paired chat when the run completes.

Manual Send

Queues results until you send them explicitly. Coming soon.

Which bot sends

Telegram Send uses the bot from the workflow's Telegram Trigger. With one trigger it binds by itself; with several it offers a picker.

Test

The Test button on the trigger fires the same run a chat message would, so you can check the wiring before leaving the desk.

A batch item, a scheduled fire and a Telegram run each go through the same door as a press on a node: the work is checked, the credits are held before anything starts, and a failed generation is not charged. The difference is only who pressed the button.