Template I/O
These two nodes exist for templates: they declare what a runner provides and what the run delivers. On a normal canvas run they simply pass values through, so you can develop and test a template like any other graph.
Template Input
Section titled “Template Input”Declares one fillable field of the template. Its name is the label the
runner sees; its type decides the widget (text box or media upload) and the
port it exposes.
| Inputs | — |
| Outputs | one port of the declared type |
| Params | name, type (text / image / video / audio), value (default / test value) |
Set value while authoring so the graph runs end-to-end without a filled
form — it’s also the default a runner starts from.
Template Output
Section titled “Template Output”Marks one deliverable of the template. Whatever is wired in is what the run
hands back, under the given name.
| Inputs | one port of the declared type |
| Outputs | — |
| Params | name, type |
Conventions
Section titled “Conventions”- Name for humans.
Product photo,Campaign brief— input names are form labels, output names label the deliverables. - One output per deliverable. A hero image and its video teaser are two Template Outputs, not one lucky wire.
- Keep test
values realistic — they’re your template’s smoke test.