> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.meetgail.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.meetgail.com/_mcp/server.

# Document Analysis

> Examines uploaded files to confirm the right documents are present and pulls key details off them.

The Document Analysis node looks through uploaded files to check whether the
documents you require are there, such as a proof of insurance or a driver's
license, and reads specific details off them where you ask. You describe what to
look for in plain terms rather than writing instructions, and the node reports
what it found, how sure it is, and the values it pulled out.

## When to use it

* You need to confirm a submission includes every required document before the
  workflow moves on.
* You want to pull specific values off a document, like a coverage amount or an
  expiration date, without reading it by hand.
* You are automating intake, where uploads arrive in different orders and you
  need to sort and verify them consistently.

## Inputs

| Field        | What it's for                                                                                                                | Example                                                                         |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| Files        | The uploaded files to examine, usually the files submitted when the workflow started.                                        | The documents attached to a new submission                                      |
| Target Items | The documents to look for. For each one you give a name, a short description, and the fields you want checked or pulled out. | A "Proof of Insurance" item with fields for coverage amount and expiration date |

For each target item you can list one or more fields to extract, each with a
name and a description of what to find on the document.

## Outputs

| Field     | What you get back                                                                                                                                                                                    |
| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Documents | One result per document you looked for: whether it was found, how confident the match is, which uploaded file it matched, the extracted field values, and whether every requested field was present. |
| Summary   | A short, plain-language recap of what the analysis found.                                                                                                                                            |

## Example

A new commercial client uploads a proof of insurance and a driver's license
during onboarding. A Document Analysis node is configured with two target items.
The first, "Proof of Insurance," asks for the coverage amount, the expiration
date, and a signature. The second, "Driver's License," asks for the expiration
date. The node reports that both documents were found, pulls the coverage amount
and dates, and flags that all requested fields were present, so a
[Conditional](/platform/workflows/node-reference/logic-and-flow/conditional) step can send
a complete submission straight through and route an incomplete one back for
follow-up.

![The Document Analysis node configuration panel, showing the files input and target items with fields to extract.](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/gail.docs.buildwithfern.com/598b9e5a94cd90aa281773477e5a2b602794c1cc9df3a3cb3c2009441b3c6a15/docs/pages/platform/workflows/assets/ai-document-analysis.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260823%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260823T232846Z&X-Amz-Expires=604800&X-Amz-Signature=798a561ff05a4f7d90bf4f7d3bd24fe0584b4945abb70bb0ad7d869c9c26a23d&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

The descriptions do the heavy lifting. Spell out what each document and field
looks like in plain terms, and branch on both whether the document was found
and how confident the match is, not just one of them. A found document with a
low confidence is worth a second look.

## Related nodes

#### [Agent](/platform/workflows/node-reference/ai/agent)

Reason over free-form text instead of checking documents.

#### [Fill PDF Form](/platform/workflows/node-reference/files-and-documents/fill-pdf-form)

Fill out a PDF once the details have been gathered.

#### [Conditional](/platform/workflows/node-reference/logic-and-flow/conditional)

Route complete and incomplete submissions down different paths.

#### [Check](/platform/workflows/node-reference/logic-and-flow/check)

Turn the analysis into a single labeled outcome.