Skip to main content
A pipeline is the processing workflow inside a pipe. It defines how documents are processed using a visual graph of connected nodes.

​
Structure

A pipeline is a directed acyclic graph (DAG) made up of:
  • Nodes: individual processing steps (triggers, actions, outputs)
  • Edges: connections between nodes that define the flow of data
Data flows from trigger nodes through action nodes and out through output nodes. A pipeline must be acyclic. You cannot create loops.

​
Validation rules

Before you can activate a pipe, its pipeline must pass validation:
  • At least one trigger node is required
  • All nodes must be connected: no orphaned nodes
  • The graph must be acyclic: no circular dependencies
  • Each node must have valid configuration (required fields filled in)
  • Edges must connect compatible node types (for example, a trigger cannot connect directly to another trigger)

​
Versioning

When you save changes to a pipeline, a new version is created. The pipeline associated with active runs continues using the version that was current when the run started. New runs use the latest saved version.

​
Visual editor

You build and edit pipelines using the visual pipeline editor. The editor provides a drag-and-drop canvas where you can add nodes, connect them with edges, and configure each node’s properties.

Pipeline editor

Learn how to use the visual pipeline editor

​
Node types

Pipelines support three categories of nodes:
  • Triggers: define how documents enter the pipeline (upload, email, HTTP)
  • Actions: process documents (extract, parse, merge, review, route)
  • Outputs: deliver results (callback, email)

Node types reference

See all available node types and their configuration