Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Engine | select | Yes | Extraction engine: Engine 1 or Engine 2 |
| Schema | schema editor | Yes | Defines the fields to extract (name, type, description) |
| Precision | select | No | Processing precision: Fast, Standard, or Advanced |
| Extraction hints | string | No | Natural language instructions to guide the AI extraction |
| JSON path | string | No | JSONPath expression to extract a subset of the output |
| Chunk size | number | No | Number of pages per chunk for large documents |
| Chunk overlap | number | No | Number of overlapping pages between chunks for context preservation |
Engines
- Engine 1: Faster, lower cost. Best for simple documents with clear structure.
- Engine 2: More capable. Best for complex documents, handwriting, or ambiguous layouts.
Chunked extraction
For large documents, you can split processing into smaller chunks. Set a chunk size (number of pages per chunk) and optionally a chunk overlap (pages shared between consecutive chunks to preserve context). Each chunk is extracted independently, and the results are combined automatically.Inputs and outputs
Allowed inputs: Trigger nodes, route, parse, review. Output: Structured JSON data matching the configured schema.Credit cost
| Engine | Precision | Cost per page |
|---|---|---|
| Engine 1 | Fast | 1 credit |
| Engine 1 | Standard | 2 credits |
| Engine 1 | Advanced | 3 credits |
| Engine 2 | Fast | 2 credits |
| Engine 2 | Standard | 3 credits |
| Engine 2 | Advanced | 5 credits |
Related
Schema design
Best practices for designing extraction schemas
Review action
Add human review after extraction
Upload and extract
Quick guide to uploading and extracting data
Parse action
Pre-process documents with OCR before extraction