> For the complete documentation index, see [llms.txt](https://help.quickappflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.quickappflow.com/workflow/ai-stages/extract-detail.md).

# Extract Detail

Select the AI option by click on +Stage.

![](/files/akJpUzPnvltr0fZD72Cp)

From the available options, select the "Extract Detail" stage.

![](/files/7cgPpWaGJytLJNajpdmG)

Once the "Extract Detail" stage is added, a configuration panel will appear, as shown below.

Enter a name in the "Stage name" field. This name should reflect the purpose or function of the extraction process.

Use the "Attachment" dropdown to select the type of document or file from which details need to be extracted. This could include images, PDFs, or other document types supported by the system.

![](/files/5LJCqJqtn6uh6QEkOnZb)

Click the "Configure" button to set up detailed extraction parameters, such as the type of data to extract, zones within the document, or specific AI models to apply.

![](/files/MrrLOD6SgOJrt5nYxX2s)

Once you have entered all necessary information and configured the extraction parameters, click on OK.

![](/files/S2Y5lSIrwZFVfhDodlrT)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.quickappflow.com/workflow/ai-stages/extract-detail.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.