Chaining tools with Forge
Build a pipeline once on a node canvas, then run it whenever you like.
- Before you start
- A job you have done by hand more than twice.
- What you end up with
- A saved, repeatable workflow that runs every step in order while the editor is open.
Step by step
-
Start from the library
Forge opens on a list of your workflows. A new one gives you an empty canvas. Building and saving a workflow is free — you only spend credits when you run it.
-
Drop nodes and wire them up
Each node is one tool, with the same options its standalone page has. Drag from a node's output socket to the next node's input to connect them. A prompt node feeding an image node feeding a spritesheet node is a complete, useful workflow.
-
Run the graph
Running executes the nodes in dependency order and hands each result to the next. Every node that produces a file costs what that tool costs — a workflow is not cheaper than doing it by hand, it is just repeatable. Keep the editor tab open while it runs: that is what moves it from one step to the next. If you close the tab the run pauses, and a step that was already generating still finishes and is kept for you; reopen the workflow to carry on.
-
Everything lands in your gallery
What your Save output nodes produce is added to your gallery alongside the standalone tools' results (vector art and documents stay in the run itself), and each run is recorded so you can see what a graph produced last time.
Worth knowing
- Most — not all — tools have a matching Forge node. The browser-only ones and the full-screen editors do not, because they need you sitting in front of them.
- If a node fails mid-run its credits are refunded like any other failure; the nodes that already succeeded keep their results. Nothing is refunded for something that was generated — a sprite sheet the browser could not build still gives you its clip.
- Change a saved workflow's settings by opening the node, not by rebuilding the graph.
- Need a set of different images — a row of item icons, a cast of portraits? Use the Image batch node: one prompt per line, up to eight, the same settings for all, each image on its own output. "Add a Save per image" wires them up, and any image you leave unwired still lands in your gallery. A line that fails is refunded on its own.
Read next