Introduction

A workflow is the named process you configure to ingest documents. Each workflow holds its configuration (a visual graph of nodes and edges), the documents you submit to it, and a history of processing runs.

​

What is a workflow?

Think of a workflow as a named process for handling a specific type of document. For example, you might create separate workflows for “Invoice Processing”, “Receipt Scanning”, or “Contract Analysis”. You configure the workflow once in the workflow editor, then send documents to it through any of its triggers.

​

Properties

​

Structure

The workflow configuration 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. The graph must be acyclic. You cannot create loops.

​

Validation rules

Before you can activate a workflow, its configuration 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)

​

Activation

A workflow must be activated before it can process documents. Activation requires a valid configuration: at least one trigger, all nodes connected, and validation passing. You can deactivate a workflow at any time to stop processing without deleting it.

​

Versioning

Every save creates a new version. A run always executes the version that was current when it started, for its entire lifetime, including across pauses for review, a Wait, or a breakpoint. New runs use the latest saved version. You can restore an earlier version, or compare any two, from the workflow editor version history. See Versions for the full history model, retention, and how to run your latest changes against a paused run.

​

Relationships

• A workflow has many documents (uploaded files)
• A workflow has many runs (one per document submitted)
• Documents submitted to a workflow trigger runs based on its configuration

​

Visual editor

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

​

Node types

Workflows support three categories of nodes:

• Triggers: define how documents enter the workflow (upload, email, HTTP)
• Actions: process documents (extract, parse, merge, review, filter, split)
• Outputs: deliver results (callback, email, forward)

​

Managing workflows

You manage workflows from the Workflows page. You can create, edit, activate, deactivate, and delete workflows.