Skip to main content
The forward output hands a document off to another pipeline for further processing. It is a terminal node. Nothing connects after it within the current pipeline; the document’s journey continues in the target pipeline, which then runs independently. Use forward outputs to chain pipelines together when one pipeline is a good fit for one stage of processing and a different pipeline is better for the next stage.
The target pipeline must contain a Forward trigger to receive the forwarded document. Pipelines without a forward trigger are not selectable.

​
Configuration

FieldTypeRequiredDescription
Target Pipelinepipeline pickerYesThe pipeline that receives the forwarded document. Only pipelines with a Forward trigger appear in the picker
When this node is placed downstream of a Route action in AI classification mode, the Target Pipeline picker is filtered to the target pipelines already chosen on the route node, so each branch lines up with the pipeline it classifies for.

​
How forwarding works

  1. The current pipeline reaches the forward output node
  2. The document is forwarded to the target pipeline
  3. The target pipeline starts a new run triggered by its forward trigger
  4. The two runs are recorded separately. You can open each one from the Runs page

​
Inputs and outputs

Allowed inputs: Any action node (extract, transform, route, merge, review, parse, validation). Output: Terminal node, no downstream connections. The document is delivered to the target pipeline’s forward trigger.

Forward trigger

Accept documents forwarded from another pipeline

Route action

Classify pages and forward each one to a different target pipeline

Callback output

Send results to an external webhook instead