> 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/requests.md).

# Requests

Create, send, track and manage document requests.

<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>Create and send a request</strong></td><td>Every option on the new request page, from recipients and reminders to language, export folder and the send dialog.</td><td><a href="/requests/create-and-send-a-request.md">Create and send a request</a></td></tr><tr><td><strong>Build your checklist</strong></td><td>Add checklist items, group them into sections, set required items and file types, attach files and reorder by drag and drop.</td><td><a href="/requests/checklists-and-sections.md">Build your checklist</a></td></tr><tr><td><strong>Open-ended requests</strong></td><td>Send a single secure upload link with no checklist, for when you don't know exactly what the recipient will send.</td><td><a href="/requests/open-ended-requests.md">Open-ended requests</a></td></tr><tr><td><strong>Bulk send</strong></td><td>Send a separate request to each row of a CSV contact list, all from one template.</td><td><a href="/requests/bulk-send.md">Bulk send</a></td></tr><tr><td><strong>Track and organize requests</strong></td><td>Find requests by status, search, tags and date, and archive, trash or restore them one at a time or in bulk.</td><td><a href="/requests/track-and-organize-requests.md">Track and organize requests</a></td></tr><tr><td><strong>Assign requests to teammates</strong></td><td>Assign a request to one or more teammates so they get its notifications and handle its review.</td><td><a href="/requests/assign-requests.md">Assign requests to teammates</a></td></tr><tr><td><strong>Expiration, completion and reopening</strong></td><td>How request links expire, what recipients see on an expired link, and how to complete, archive and reopen requests.</td><td><a href="/requests/expiration-and-reopening.md">Expiration, completion and reopening</a></td></tr><tr><td><strong>Send requests in another language</strong></td><td>Send a request in Spanish, French, Portuguese, Russian or Chinese, with translated emails and upload page.</td><td><a href="/requests/translations.md">Send requests in another language</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/requests.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.
