> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/reviewing-and-exporting.md).

# Reviewing & exporting

Review what comes back, then download it or send it to your cloud storage.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Understanding reviews</strong></td><td>Review what recipients send with checklist item reviews, which notify them, and file reviews, which don't. Then mark the request complete.</td><td><a href="/reviewing-and-exporting/understanding-reviews.md">Understanding reviews</a></td></tr><tr><td><strong>Download and export to PDF</strong></td><td>Preview files in your browser, download one file or a selection, or export a whole request as a zip file or a single merged PDF.</td><td><a href="/reviewing-and-exporting/download-and-pdf-export.md">Download and export to PDF</a></td></tr><tr><td><strong>Cloud storage integrations and auto-export</strong></td><td>Connect Google Drive, Dropbox, Box, Microsoft 365, Clio or Zoho WorkDrive, export a request's files into organized folders, and set up auto-export.</td><td><a href="/reviewing-and-exporting/cloud-storage-and-auto-export.md">Cloud storage integrations and auto-export</a></td></tr></tbody></table>


---

# 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://support.pipefile.com/reviewing-and-exporting.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.