> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ingestly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> Definitions for the core terms used across Ingestly.

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

<AccordionGroup>
  <Accordion title="Action node">
    A pipeline node that processes data between a trigger and an output. Actions include [parse](/nodes/parse), [extract](/nodes/extract), [classify](/nodes/classify), [filter](/nodes/filter), [split](/nodes/split), [merge](/nodes/merge), [review](/nodes/review), [transform](/nodes/transform), [validation](/nodes/validation), and [HTTP action](/nodes/http-action).
  </Accordion>

  <Accordion title="Activation">
    The state that lets a pipeline accept new documents and execute runs. Activation requires a valid configuration with at least one trigger. See [pipelines](/pipelines/introduction#activation).
  </Accordion>

  <Accordion title="Alert rule">
    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](/admin/alert-rules).
  </Accordion>

  <Accordion title="API key">
    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](/admin/api-keys).
  </Accordion>
</AccordionGroup>

## C

<AccordionGroup>
  <Accordion title="Callback">
    A webhook notification Ingestly sends to an external URL when a run completes. Configured with the [callback output](/nodes/callback) node.
  </Accordion>

  <Accordion title="Child run">
    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](/runs/introduction#document-chunking).
  </Accordion>

  <Accordion title="Connector">
    An OAuth integration that lets pipeline nodes (like [HTTP action](/nodes/http-action)) call an external service without exposing credentials. See [connectors](/admin/connectors).
  </Accordion>

  <Accordion title="Credit">
    The billing unit consumed per pipeline run. Each node type has its own credit cost; see [credits](/admin/credits) for the full breakdown.
  </Accordion>
</AccordionGroup>

## D

<AccordionGroup>
  <Accordion title="Document">
    A file uploaded to a pipeline for processing. Ingestly supports PDF, JPEG, PNG, TIFF, and HEIC. See [documents](/files/introduction).
  </Accordion>

  <Accordion title="Document chunking">
    Splitting a multi-page document into separate chunks that each run through the pipeline as a [child run](#child-run). See [runs](/runs/introduction#document-chunking).
  </Accordion>
</AccordionGroup>

## F

<AccordionGroup>
  <Accordion title="Failure action">
    Configurable behavior on a [validation](/nodes/validation) node when validation errors occur. `Fail` stops the run; `Warn` lets the run continue with warnings attached.
  </Accordion>

  <Accordion title="Forward trigger">
    A trigger that receives forwarded documents and reference samples for AI similarity classification. See [forward trigger](/nodes/forward-trigger).
  </Accordion>
</AccordionGroup>

## N

<AccordionGroup>
  <Accordion title="Node">
    A single step in a pipeline. Nodes are grouped into three categories: triggers, actions, and outputs.
  </Accordion>
</AccordionGroup>

## O

<AccordionGroup>
  <Accordion title="Organization">
    The top-level account in Ingestly. Each organization holds workspaces, users, API keys, billing, and a credit balance.
  </Accordion>

  <Accordion title="Output node">
    A pipeline node that delivers final results out of Ingestly. Outputs include [callback](/nodes/callback), [email output](/nodes/email-output), and [forward output](/nodes/forward-output).
  </Accordion>
</AccordionGroup>

## P

<AccordionGroup>
  <Accordion title="Pipeline">
    The named workflow you configure for document ingestion. A pipeline 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 [pipelines](/pipelines/introduction).
  </Accordion>

  <Accordion title="Pipeline editor">
    The visual canvas where you build a pipeline by dragging in nodes and connecting them. See [pipeline editor](/pipelines/editor).
  </Accordion>

  <Accordion title="Pipeline group">
    A workspace-scoped grouping that lets you organize related pipelines by name and color on the Pipelines page. See [managing pipelines](/pipelines/managing#pipeline-groups).
  </Accordion>
</AccordionGroup>

## R

<AccordionGroup>
  <Accordion title="Retention">
    The number of days Ingestly keeps processed documents and run data for a pipeline. Configured per pipeline.
  </Accordion>

  <Accordion title="Review queue">
    The list of paused runs waiting for a human to inspect and approve. See [review queue](/reviews/queue).
  </Accordion>

  <Accordion title="Review task">
    A pause point in a run created by a [review](/nodes/review) node. A reviewer can edit and approve the data before the run continues.
  </Accordion>

  <Accordion title="Run">
    One execution of a pipeline, triggered when a document is submitted to it. See [runs](/runs/introduction).
  </Accordion>
</AccordionGroup>

## S

<AccordionGroup>
  <Accordion title="Schema">
    The JSON Schema (Draft-07) definition that tells the [extract](/nodes/extract) node which fields to pull from a document. See [schema design](/guides/schema-design).
  </Accordion>

  <Accordion title="Step execution">
    The result of a single node within a run. Captures input, output, status, timing, and any errors for that step. See [step executions](/runs/introduction#step-executions).
  </Accordion>
</AccordionGroup>

## T

<AccordionGroup>
  <Accordion title="Trigger node">
    The first node in a pipeline. Defines how documents enter the pipeline: [upload](/nodes/upload-trigger), [email](/nodes/email-trigger), [webhook](/nodes/webhook-trigger), or [forward](/nodes/forward-trigger).
  </Accordion>
</AccordionGroup>

## U

<AccordionGroup>
  <Accordion title="Unverified field">
    A field whose extraction confidence falls below an internal threshold when **Field confidence** is enabled on the [extract](/nodes/extract#unverified-fields) node. Pair with a review node configured to **Pause mode = Unverified Fields** to send uncertain runs to human review.
  </Accordion>
</AccordionGroup>

## W

<AccordionGroup>
  <Accordion title="Webhook signing key">
    The HMAC-SHA256 secret Ingestly uses to sign callback requests so your application can verify they came from Ingestly. See [webhook signing keys](/admin/webhook-signing-keys).
  </Accordion>

  <Accordion title="Workspace">
    An isolated container for pipelines, documents, and runs inside an organization. Pipelines in one workspace are not visible from another. See [workspaces](/admin/workspaces).
  </Accordion>
</AccordionGroup>