Extract Fields

The Extract Fields node uses AI vision to pull specific named values from images and documents. Unlike OCR (which extracts all text) or Table Extract (which finds tabular data), Extract Fields targets the exact fields you define: invoice number, due date, total amount, customer name.

Extract Fields node
Extract Fields: pull specific named values

When to use Extract Fields vs. other Vision nodes

NodeUse when
OCRYou need all text from an image
Read PDFYou need all text from a PDF
Table ExtractThe data is in a table/grid format
Extract FieldsYou need specific named values from a document
Ask DocumentYou want to ask a natural language question about a document

Configuration

FieldTypeRequiredDescription
SourceSelectYesWhere the image/document comes from: URL, File upload output, or previous node
Source URL/pathFX formulaYesThe image URL or file path. Supports variables.
Fields to extractField listYesDefine each field you want to pull (see below)
Document typeSelectNoHint: Invoice, Receipt, ID card, Contract, Custom. Helps AI accuracy.

Defining fields

Each field has:

PropertyDescription
Field nameThe key in the output (e.g., invoice_number)
Field labelHuman-readable description (e.g., "Invoice Number" or "The invoice/PO number at the top of the document")
Field typeExpected type: Text, Number, Date, Currency, Boolean
RequiredWhether extraction should fail if this field isn't found

Example field configuration for invoices

Field nameLabelTypeRequired
invoice_numberInvoice or PO numberTextYes
dateInvoice dateDateYes
due_datePayment due dateDateNo
vendor_nameVendor / company nameTextYes
total_amountTotal amount dueCurrencyYes
tax_amountTax / VAT amountCurrencyNo
line_items_countNumber of line itemsNumberNo
payment_termsPayment terms (Net 30, etc.)TextNo

Output variables

{{extract_fields.result.invoice_number}}   → "INV-2024-0847"
{{extract_fields.result.date}}             → "2024-03-15"
{{extract_fields.result.total_amount}}     → 4250.00
{{extract_fields.result.vendor_name}}      → "Acme Supplies Inc."
{{extract_fields.confidence}}              → 0.94

Each field is available at {{extract_fields.result.<field_name>}}. The confidence score (0-1) indicates how confident the AI is about the overall extraction.

Common patterns

Invoice processing

Email Trigger (new email with attachment) → Extract Fields (invoice fields) →
  If-Else (total > 5000?) →
    Yes: HITL (manager approval) → Create Record (accounting DB)
    No: Create Record (accounting DB) → Send Email (auto-approved notification)

Receipt expense tracking

Form Submission (receipt upload) → Extract Fields (vendor, amount, date, category) →
  Google Sheets (append to expense report) → If-Else (amount > policy limit?) →
    Yes: Slack (notify manager for approval)

ID verification

Form Submission (ID upload) → Extract Fields (name, DOB, ID number, expiry) →
  TinyGPT (verify name matches form submission) → If-Else (match?) →
    Yes: Update Record (verified = true)
    No: Send Email (verification failed, please re-upload)

Tips for better extraction

TipWhy
Set the document typeGives the AI context about where to look for fields
Write descriptive labels"Total amount including tax at the bottom" is better than "Total"
Use specific field typesCurrency type handles $ symbols and decimal parsing automatically
Mark truly required fieldsDon't mark everything required; some documents may lack optional fields
Provide multiple name variants"Invoice Number / PO Number / Reference Number" in the label handles different document formats
Warning

Extraction accuracy depends on document quality. Blurry photos, handwritten text, or unusual layouts may produce lower confidence scores. Always validate extracted data for high-stakes workflows (financial, legal) with a Human-in-the-Loop node.

Note

Extract Fields costs 5 credits per execution. The cost is the same regardless of the number of fields defined.