> For the complete documentation index, see [llms.txt](https://docs.empowergpt.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empowergpt.ai/workflows/workflow-usecases/smart-pdf-extractor.md).

# Smart PDF Extractor

### Problem Statement

Consider a purchasing professional who receives invoices from multiple vendors and needs to review and compare them.

To perform the comparison manually, the user would need to open each invoice individually, identify the required information, and enter the relevant values into an Excel sheet.

For a small number of invoices, this may be manageable. However, if there are 100 invoices, the same process needs to be repeated 100 times. This makes the process repetitive and time-consuming and increases the possibility of manual data-entry errors.

<div data-with-frame="true"><figure><img src="https://2192711725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc2KRGWrkyRO0iZN5Lyeg%2Fuploads%2FMircHEEJTqmCzZIvS0HH%2Fimage.png?alt=media&amp;token=ea4f0395-9667-482f-af22-c2ea2ab0cf2f" alt=""><figcaption></figcaption></figure></div>

### Solution Using Workflows

The **Smart PDF Extractor** automates this process.

Instead of reviewing each PDF manually, users can upload multiple invoices at once. The workflow processes the PDF files, extracts the required information, and consolidates the extracted data into an Excel file.

Each PDF is processed individually, while the final results are brought together in a structured Excel output.

### Using Smart PDF Extractor

1. Go to **Workflows** and select **Smart PDF Extractor**.
2. Open the **Agent Block**.
3. In the Agent configuration, define the fields that you want to extract from the invoices or other PDF documents.
4. The workflow is automatically saved.
5. Click **Run**.
6. Upload all the PDF files that you want to process.
7. Submit the form.
8. The workflow automatically processes each PDF and extracts the configured information.
9. The extracted information is written to an Excel file.
10. Once the workflow completes, download the generated Excel file from the **Output Block**.

### How It Works

The overall process is:

**Upload PDF Files → Process PDFs → Extract Required Fields → Consolidate Data → Generate Excel File**

For example, when processing vendor invoices, you could configure the Agent to extract fields such as:

* Vendor Name
* Invoice Number
* Invoice Date
* Purchase Order Number
* Total Amount
* Tax Amount
* Currency

The workflow processes the uploaded invoices and creates an Excel file containing the extracted information, making it easier to review and compare the invoices.

### Result

Instead of manually opening and reviewing every invoice, the user receives a structured Excel file containing the required information from all uploaded PDFs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.empowergpt.ai/workflows/workflow-usecases/smart-pdf-extractor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
