Skip to main content
Nodes are the building blocks of pipelines. You connect them with edges to define how data flows from start to finish. Nodes are divided into three categories that follow the natural flow of data:
  • Triggers bring documents in
  • Actions process them
  • Outputs deliver the results

Triggers

Trigger nodes define how documents enter the pipeline. Every pipeline must have at least one trigger.

Upload trigger

Accept documents uploaded through the UI

Email trigger

Receive documents via an auto-generated email address

Webhook trigger

Accept documents submitted via the API

Actions

Action nodes process documents and transform data. You can chain multiple actions together.

Parse action

Extract raw text from documents using OCR

Extract action

Pull structured data from documents using AI

Review action

Pause for human review and approval

Transform action

Convert data to CSV, JSON, XML, or Excel

Route action

Send documents down different paths based on conditions

Merge action

Combine data from multiple branches

Validation action

Validate data with rules, schemas, expressions, endpoints, scripts, or AI

HTTP action

Call an external HTTP endpoint and use the response

Outputs

Output nodes deliver results outside DocPipe. They are always the last step in a pipeline path.

Callback output

Send results to an external webhook URL

Email output

Send results via email

Beta nodes

Some nodes are marked with a Beta badge in the pipeline editor. Beta nodes are fully functional but may change in future releases. Currently, the merge action and HTTP action are in beta.

Summary

NodeCategoryCredit costDescription
Upload triggerTrigger0Accept documents uploaded through the UI
Email triggerTrigger0Receive documents via email
Webhook triggerTrigger0Accept documents via the API
Parse actionAction1–2 per pageOCR text extraction
Extract actionAction1–5 per pageAI-powered structured data extraction
Review actionAction0Human-in-the-loop review step
Transform actionAction0Format conversion (CSV, JSON, XML, Excel)
Route actionAction0–0.5Conditional routing
Merge actionAction0Multi-branch data merge
Validation actionAction0–LLMData validation with rules, schemas, expressions, endpoints, scripts, or AI
HTTP actionAction0External HTTP endpoint integration
Callback outputOutput0Webhook delivery
Email outputOutput0Email delivery