Skip to main content
Triggered when the document processing pipeline finishes, whether or not extraction actually ran.

Event Type

document.extracted

Description

This event fires once per document outcome: completed when the pipeline finished (extraction may have been skipped because validation flagged the document), and failed when extraction itself errored. The payload always includes a classification object describing which checklist item(s) the document matched, with per-item validation results on each matched item.

Payload Structure

string
required
The event type, always document.extracted
string
required
ID of the workspace this event belongs to
string
required
ID of the lead this document belongs to
string
required
External ID of the lead this document belongs to, if one was provided at creation
string
required
ID of the document that was processed
string
External identifier for the document, if one was provided at creation
string
required
completed when the pipeline finished or failed when extraction errored
string
ID of the parent action that triggered the pipeline
string
One- to two-sentence document summary from OCR, when available (same as stored on the document)
string
Inferred document type from OCR (same as the type column on documents, e.g. Bank Statement, Tax Return). null when not set.
object
required
How the document was classified before extraction (or an empty match list with a no-match reason)
object
required
Returns any checklist items extracted from documents.

Examples

Successful extraction

Completed with validation failure

When at least one matched checklist item has validation.status: "invalid", extraction is not run, but the pipeline still reports status: completed. extractionResult is still present with an empty items array and extractedCount: 0; the per-item validation block on each matched item carries the failure reasons (null when no rules ran).