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

​
Configuration

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

​
How forwarding works

  1. The current pipeline reaches the forward output node
  2. The document is forwarded to the target pipe
  3. The target pipe 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 pipe’s forward trigger.

Forward trigger

Accept documents forwarded from another pipe

Route action

Classify pages and forward each one to a different target pipe

Callback output

Send results to an external webhook instead