> 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/getting-started/send-your-first-request.md).

# Send your first request

Create an account, build a short checklist and send your first request in a few minutes.

A request is a secure link you send to a recipient. They open it, upload what you asked for, and you collect everything in one place. Recipients don't need an account, a password or any software.

{% hint style="info" %}
New accounts start with a 14-day free trial that includes the **Professional** feature set. See [Plans and features](/getting-started/plans-and-features.md).
{% endhint %}

{% stepper %}
{% step %}

### Create your account

Sign up at <https://pipefile.com/register>. After you verify your email, you land on your dashboard.
{% endstep %}

{% step %}

### Start a new request

Click **New Request** at the top of the left sidebar. The **Create New File Request** page opens.

The arrow next to **New Request** opens your templates, so you can start from one later. See [Send from a template](/templates/send-from-a-template.md).
{% endstep %}

{% step %}

### Add your recipient

Under **Recipients**, type the person's name and **Email Address**. Pipefile suggests matches from your [contacts](/team-and-account/contacts.md) as you type. To send the same request to more people, click **Add CC Recipient**.
{% endstep %}

{% step %}

### List what you need

Leave **Checklist** selected and fill in the first checklist item:

* **Document Name**, for example "Photo of ID".
* **Instructions** (optional), for example "Driver's license or passport".

Click **Add Item** for each additional document. See [Build your checklist](/requests/checklists-and-sections.md) for sections, required items and file types.
{% endstep %}

{% step %}

### Check reminders and expiration

Under **Reminders**, Pipefile sends a reminder every 3 days and the request expires in 30 days. Change either if you need to.
{% endstep %}

{% step %}

### Send it

Click **Next**. In the **Send Request** dialog, enter a **Subject** (for example "Documents for your 2026 return") and an optional message, then click **Send Request**.

Your recipient gets an email with a link to the request. The confirmation shows the same link so you can share it another way.
{% endstep %}
{% endstepper %}

Pipefile saves your work as a draft while you build the request. If you leave before sending, find it under **All Requests** > **Drafts**.

## What happens next

* Your recipient opens the link and uploads each document against its checklist item. They can also mark an item **Not Applicable** if it isn't marked required.
* Pipefile emails you as files arrive, and sends reminders until the checklist is complete or the request expires.
* Open the request from your **Inbox** to review and download what came in. See [Understanding reviews](/reviewing-and-exporting/understanding-reviews.md).

{% hint style="success" %}
Sending the same list often? After your first send, Pipefile offers to save the request as a template. You can also click **Save as Template** in the **Send Request** dialog.
{% endhint %}

## Prefer to describe it?

The AI Assistant opens on the new request page. Describe what you need in plain language, and it builds a draft checklist for you to review before anything is sent. See [AI Assistant](/ai-assistant.md).

## Related

* [Create and send a request](/requests/create-and-send-a-request.md): every option on the request page
* [Track and organize requests](/requests/track-and-organize-requests.md)
* [Free training](/getting-started/free-training.md)


---

# 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/getting-started/send-your-first-request.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.