pipeline.output

A terminal node — where a branch's result comes out. Each pipeline.output becomes its own job, so the number of outputs is the number of jobs (and credits) a submit spends.

Config

FieldTypeDefaultNotes
suffixstring""Labels the output. Returned as outputon the job and appended to the result filename, so a fan-out's files don't collide.

One output = one job = one credit

The server splits your graph into a self-contained job per pipeline.output. A two-output graph over ten files is twenty jobs — M files × N outputs credits. Each output retries on its own. See Auth & billing for the meter.

In a pipeline

{
  id: 'thumb-out',
  type: 'pipeline.output',
  config: { suffix: { value: 'thumb' } },
}

In the SDK results, that label surfaces as output on each entry:

for (const out of result.outputs) {
  console.log(out.output, out.media.url); // 'thumb' → …, 'hero' → …
}
A queue always has a single output, so runQueue adds one for you. Reach for a graph when you want more than one output per input.