pipeline.input
The entry point of every graph. The uploaded source enters here, and each branch of operations starts from an edge off this node. It carries no config.
Rules
A graph must have exactly one pipeline.input. Validation fails with NO_INPUTif it's missing. It takes no config — the source bytes and their content type come from the file you submit, not from the node.
In a pipeline
{ id: 'in', type: 'pipeline.input' }Fan-out starts here: draw an edge from the input to each branch, and each branch ends at its own pipeline.output.
edges: [
{ source: 'in', target: 'thumb-resize' }, // → thumbnail branch
{ source: 'in', target: 'hero-resize' }, // → hero branch
]You never construct this node manually with the SDK's
runQueue— it's added for you. You only hand-write it when building a graph for runPipeline.