agenthub · output.image
Image Output
Show the generated image or images as the workflow's result. A terminal node — nothing runs after it.
Why the node earns its place
Generation produces data URIs; something has to say this is the answer, render it. This node returns a single assistant message whose content carries an image marker plus the images, and the gallery surface detects that marker and renders them.
It is deliberately dumb about where images came from. It flattens whatever arrives — a single string, a list, or a merged bag keyed by source node when several edges fan in — so a two-branch image workflow needs no adapter before it.
How it works at run time
- 1Prefer the
imagesarray; fall back to the singleimage. - 2Flatten a fan-in bag into one list and drop anything that is not a non-empty string.
- 3Emit the assistant message carrying the marker and the images; the run collects it as an output.
What you wire
Inputs
- imagestring
- imagesarray
Outputs
Nothing handed onward.
Configuration
Nothing to configure — this node has no settings of its own.
What usually goes wrong
Watch for this
Nothing downstream of this node runs — it has no output ports at all. If you need the images and a reply, wire both from the generating node rather than trying to chain past this one.
Behaviour & provenance