Skip to main content
This glossary covers the terms you’ll see throughout the dashboard, the API, and the rest of these docs. Entries are alphabetical; click any term to expand its definition.

​
A

A workflow node that processes data between a trigger and an output. Actions include parse, extract, classify, filter, split, merge, review, transform, validation, and HTTP action. The Business Central and QuickBooks connector nodes are actions too: they look up, create or update records, and in a write operation they can end a path.
The state that lets a workflow accept new documents and execute runs. Activation requires a valid configuration with at least one trigger. See workflows.
A monitoring rule that fires a notification when a metric crosses a threshold (for example, a failure rate above 10% or a credit balance below 500). See alert rules.
A credential that authenticates programmatic requests to the Ingestly API. Keys use the ing_ prefix and are passed in the X-Api-Key header. See API keys.

​
C

A webhook notification Ingestly sends to an external URL when a run completes. Configured with the callback output node.
A run created to process a single chunk of a document split by a parent run. The parent waits in the Awaiting Children status until every child run finishes. See runs.
An OAuth integration that lets workflow nodes (like HTTP action) call an external service without exposing credentials. See connectors.
A highlight whose value is printed more than once in the document, where the box could have landed on another copy of it. The extracted value is not in question, only which copy the box points at. See contested bindings.
The billing unit consumed per workflow run. Each node type has its own credit cost; see credits for the full breakdown.

​
D

A file uploaded to a workflow for processing. Ingestly supports PDF, JPEG, PNG, TIFF, GIF, WebP, and CSV, plus Word, Excel, PowerPoint, OpenDocument, and Rich Text documents (the legacy .doc, .xls, and .ppt binaries are not accepted). See documents.
Splitting a multi-page document into separate chunks that each run through the workflow as a child run. See runs.

​
F

Configurable behavior on a validation node when validation errors occur. Fail stops the run; Warn lets the run continue with warnings attached.
A trigger that receives documents sent by another workflow’s forward node. See forward trigger.

​
H

A document a workflow trigger received with Run automatically turned off, or one assigned to a workflow from an inbox. It belongs to a workflow and waits until someone runs it: under Held in the inbox it came from, or under Workflows beneath its own workflow when a trigger held it. See Held documents.

​
I

A user-created intake address that belongs to no workflow. Documents emailed or uploaded to it wait as Unassigned until a person, or one of the inbox’s routing rules, assigns them to a workflow. An inbox has its own allowed senders, accepted formats, size cap and expiry. See Inbox.

​
N

A single step in a workflow. Nodes are grouped into three categories: triggers, actions, and outputs.

​
O

The top-level account in Ingestly. Each organization holds workspaces, users, API keys, billing, and a credit balance.
A workflow node that delivers results out of Ingestly. Outputs include callback, email output, and forward output. Most outputs end a path. The callback output is the exception: it hands the receiving system’s response to the steps after it.

​
P

The named process you configure for document ingestion. A workflow holds its configuration (a directed graph of nodes and edges), its documents, and its run history. Surfaced consistently across the UI, the API, and runs. See workflows.
The visual canvas where you build a workflow by dragging in nodes and connecting them. See workflow editor.
A workspace-scoped grouping that lets you organize related workflows by name and color on the Workflows page. See managing workflows.

​
R

The number of days Ingestly keeps processed documents and run data for a workflow. Configured per workflow. Held documents age out on the same schedule, counted from when they arrived. A document still unassigned in an inbox follows the inbox’s own expiry instead, until it is assigned. Only documents still in Processing are exempt.
The list of paused runs waiting for a human to inspect and approve. See review queue.
A pause point in a run created by a review node. A reviewer can edit and approve the data before the run continues.
An ordered rule on an inbox that assigns an arriving document (emailed or uploaded) to a workflow when its sender or subject matches, or when it is the same kind of document, from the same issuer, as the rule’s sample document. The first matching rule applies, and the document is held on the workflow rather than run. See Route documents automatically.
One execution of a workflow, triggered when a document is submitted to it. See runs.

​
S

The one document a routing rule or a Classify example holds as its reference: an arriving document or a classified page matches when AI judges it the same kind of document, from the same issuer, as the sample (“documents like this match”). When AI is unavailable, word similarity decides. See Route documents automatically and Classify.
The JSON Schema (Draft-07) definition that tells the extract node which fields to pull from a document. See schema design.
The result of a single node within a run. Captures input, output, status, timing, and any errors for that step. See step executions.

​
T

The first node in a workflow. Defines how documents enter the workflow: upload, email, webhook, or forward.

​
U

The status of a document that arrived in an inbox, has been parsed, matched none of the inbox’s routing rules, and is waiting for a person to assign it to a workflow. It expires on the inbox’s expiry, counted from arrival, until it is assigned.
A field whose value the matcher could not place on the page: the value was extracted, but no region of the document matched it closely enough to highlight. Independent of the Field confidence toggle. See extract.

​
W

The HMAC-SHA256 secret Ingestly uses to sign callback requests so your application can verify they came from Ingestly. See webhook signing keys.
An isolated container for workflows, documents, and runs inside an organization. Workflows in one workspace are not visible from another. See workspaces.