Skip to main content
A workflow is a graph of nodes. Each node does one job on the document: read it, pull fields out of it, sort it, split it, check it, fill it in, or tell someone about it. You connect nodes on the Studio canvas, or send the same graph to the API as nodes and edges. Most workflows are two nodes: Parse then Extract. The rest exist for documents that are more complicated, or for when you want something other than data back.

​
The palette

The Studio palette groups nodes the same way this table does. Knowledge appears in the palette once the feature is enabled for your organization.

​
Three shapes you will build

Read only. Parse alone. You get the document as markup, for search, your own model, or an archive. Read, then pull out. The default: “read this document and give me these fields”. Sort first, then pull out. Classify decides the kind of document, then sends it to an Extract tailored to that kind. Split works the same way for files that hold several documents. Add Validate after an Extract to check the values, If/Else to branch on them, and an alert at the end of a branch to tell someone.

​
Every node page reads the same way

  1. What the node does and where it sits in the palette.
  2. The node as code: API JSON, then the Python and TypeScript SDK call.
  3. The Studio panel.
  4. Every option, its type, default and what it does.
  5. What can feed it and what it can feed.
  6. What it costs.
  7. Examples that use it.
Start with Parse.